Where can I get some fairly clear info on modifying the context menu?
I've read through the FAQs and Tutorials but the information there is kind of sparse and doesn't really explain how to make changes very well -- at least not to me.
For example, the Tutorial on Context Menus mentions that you can now add one command to show all the 3rd party menu items in a submenu, but it goes no further in explaining how or where to change that. It shows the command as follows:
[quote]A new and related function has been added to Opus since the tip was made. If you hide 3rd party context menu items you can use this command to show them all in the same place (eg a submenu) without having to list each one explicitly.
But it doesn't say exactly where to enter that command. I have tried it in several places and manners in the "Edit File Type" dialog, but all I get is errors when I try to test it.
Learning by trial and error in the context menu could get risky, I imagine, but I cannot find any more explanatory information on this.
Can anyone tell me where I can find some instructional details for customizing the context menus? Something that not only throws out the commands but explains where and how to enter them?
In "Edit File Type", open "All files and folders". in context menu tab, create new and select type "Sub-menu (not supported in Explorer)".
now create command under sub-menu by clicking new button and select "Run an Opus function (not supported in Explorer)" and add command "Filetype CONTEXTMENU CONTEXTOPTIONS=windowsonly".
after you can enable "Hide Windows items on file context menus" in Preferences/Miscellaneous - Windows Integration
I already tried something very much like that - I thought it was exactly like that, but I'll give it another try and hope I don't crash it again. (Crashed it most all day the other day trying to get this right).
First off... I can't advocate enough to use the Settings->Backup & Restore menu option. What you said about 'messing things up' while trying to play around with the context menu can be true in some cases... but there are a few things you can do to help protect yourself and get back to a known, good, working configuration with a minimum of fuss.
Using the Backup & Restore option is one of those things... Another is to understand how Opus modifies the context menu... There a few types of context menu actions you can add; two of which will modify the registry and apply to both Opus and Explorer... while the other two are Opus specific and only get stored in the Opus xml based config files.
Since you've asked about the Filetype CONTEXTMENU CONTEXTOPTIONS=windowsonly the 'All files and folders' file type is a usual and good spot to put such a thing like Albator suggested... and like he also mentioned, you'd want to be sure to add it as an action of Type: Run an Opus function (not supported in Explorer).
I can't think of any way doing this would causes a CRASH though...
What did you do right before the crash...?
Maybe you clicked on the menu you added that runs the windowsonly action? If so, assuming you already had the "Hide Windows items on file context menus" option enabled that Albator mentioned... does the same crash happen if you just click the RMB with the shift key held down (this temporarily bypasses the 'hide windows items' suppression of the full context menu)?
Is it while you click RMB on a certain filetype that it happens?
Opus should exclude calling any shell extension that has caused something like that to happen due to a weird compatability issue... but maybe it doesn't exlcude calling into 'conflicting' shell extensions when you access them through the windowsonly maneuver or something weird like that...
Sorry not to get back right away - I don't remember getting an email about your reply.
As for "crashing", I used the term inappropriately - I didn't crash my Windows session; I just rendered either all context menus in DOpus inoperable, or froze DOpus and had to correct and restart it.
I tried so many different locations with the commands I can't remember specifically which caused what now. And I'm in no hurry to try and replicate them!