I am following the tutorial available here. i had 2 questions regarding this
While accessing Settings > Preferences > Miscellaneous > Shell Extensions > Context Menu, how do i hide handlers for apps which are not present in there, Is there any way out ?
Is there a way to hide a particular handler conditionally ? For example. I have "Open with Code" handler from vscode but i don't want it to appear every time, say i have selected a file which is exe executable, archive, video etc, i want to hide it
In File Explorer, i did all of this using a open source tool called Nilesoft Shell. i am wondering if this functionality can be achieved with Directory Opus
If you want to hide most / a lot of things, the best way is usually to turn on the option that hides all of them, then add back the specific items you want to see all the time. (You can always hold Shift when right-clicking to see the hidden items if you need one you don't use often enough to add back into the menu.)
When doing that, you can add the items to a specific file type if you only want them to appear for that type. (You could also use modifiers like @ifsel to make items conditional, if more complex rules are needed than just the file type.)
Items that aren't in the Shell Extensions list are usually added via registry values which specify the menu item name and command as static data. (OTOH, Shell Extensions are DLLs containing code which gets run every time the menu is displayed and can to add items to the menu programmatically.) The registry-only items may be editable via Settings > File Types, and if not via RegEdit. There are so many different ways things can add to menus in Windows these days that it's hard to provide complete instructions.
Thanks for the heads up, i now realize its the best way to for me to just hide all of them and explicitly add back ones i need.
Referring the earlier linked doc, i am able to restore individual app's context menu handler through its CLSID successfully although i am having a hard time restoring sub menu. For instance, i am trying to add back Open With submenu. In Settings -> File Types -> All files and folders (directory opus file types), i can create a new submenu but this usecase is for explicitly including multiple handlers inside it. i am guessing there must a separate way to add back stock submenu as it is from the original context menu ? Might be a good idea to add it in docs as well
//The "Filetype OPENWITHMENU" command is designed only for a context menu
//per https://resource.dopus.com/t/menu-button-enabled-only-when-file-is-selected/19834/8
//Do not click on the button
//@disablenosel:files or @disablenosel:numfiles=1 do not work to turn off the button if only a single files is selected
//
//Hover over the button to see a list of programs that open the selected file
FileType OPENWITHMENU
Lastly, what is the command syntax to restore UWP apps if anyone has tried it ?
For instance, i am trying to add back Open in Terminal which is handler for Windows Terminal being a UWP app. From Settings -> Preferences -> Miscellaneous -> Shell Extensions -> Context Menu (UWP), i got its CLSID which happens to be Microsoft.WindowsTerminal_1.21.2911.0_x64__8wekyb3d8bbwe
Then in Settings -> File Types -> All folders -> Context Menu, I created a new opus function with the following command FileType CONTEXTFORCE CONTEXTMENU=8wekyb3d8bbwe, it doesn't seem to work, maybe i am doing the syntax wrong since i can't really find any example
Thanks for tip for Terminal specifically although i am looking forward to add back some other UWP app handlers to context menu as well so would to great know the proper function syntax.
That seems like its a guide to add UWP apps to a third party software known as slickrun. Anyways, as mentioned in docs, this is very well supported in Dopus, i will do some trial/error with the function FileType CONTEXTFORCE CONTEXTMENU=XXX to see if i can get it working
I will update the ones i have found to be not working here
Hello @Leo sorry for the ping but can you maybe have a look at this for proper confirmation. If it happens to be a bug, i would file it as such in a new report. Restoring UWP apps individually just won't work for some reason.
With UWP context menus, there would not be any {} around the identifiers (those are part of the big hex number in brackets CLSIDs that identify normal, non-UWP context menus).
This is assuming it works with UWP at all. I am not sure it's intended to. (Not easy for me to check on the machine I am on as it has no UWP context menus installed.)
Please link your account if you want to request a change here or further testing/help with it.
I am using Dopus v13.11. Currently on the trial period while i migrate my nilesoft shell's config around here.
Regarding adding UWP context menu handler, it doesn't work even without the {}
Yes correct, I had discovered Dopus & accordingly joined forum before the public release of Dopus 13. Since Dopus 13 was a upcoming major upgrade, i didn't want to spend time learning my way around v12. So i decided to wait for the public release of v13. I only got around trying it finally couple of days back.
Not being a power user like many here, the tons of stuffs dopus offers is definitely a bonus for me as i dig deep into it & figure out usecases. Although my initial plan is to first try replacing the only single software i used for file explorer - Nilesoft shell which provided great control over context menus.
Dopus seems to be doing everything it can and even extra, it's just stuck on adding back individual UWP app handler after hiding all.
Well i never denied having installed Dopus before. The nature of questions in my posts you linked being way too basic also indicate it's something one would ask 5 mins into trying a file manager.
I just told that this is very first time i have registered with my email and seriously using dopus 24/7 from few days. Again this current post is a indication of that being much more involved.
I can blame my laziness but i don't see the any problem with this, i just forgot about it earlier.
Thiojoe made a youtube video a week ago wherein he made a super useful tool & since he uses Dopus exclusively, it reminded me of Dopus, i thought to give it a real shot this time around
It made me curious what it was until I found out he made a really cool tool. Hopefully he will share it here, I believe it will be very useful for many people.
(You'll Want To See This)