As I understand it, if I make a change using the Opus Settings --> File Types dialog - e.g. to add/modify the double click action for a specific file type - Opus creates or modifies a corresponding OXR file in /dopusdata/FileTypes and also applies a registry change. If I save my config and restore on another PC, the OXR file is present and contains the relevant Opus command(s) but the registry change is not.
Other than repeating the change in its entirety on the second system, is there a simple way of getting the relevant registry update applied?
Whether the change goes into the .oxr file or into the registry depends on the type of change. Changes that Explorer and other programs can understand have to go into the registry, else they would only be seen in Opus. On the other hand, changes that only Opus can understand can be kept in the config file since nothing else would use them even if they were in the registry.
There isn't a way to extract the changes made to the registry, since they're made directly to the registry and are then just part of your registry. Opus itself doesn't know that the change was made via its filetype editor. Making those changes using Opus is no different to making them using RegEdit, and they become part of your Windows configuration rather than the Opus configuration.
If you do want changes to remain part of your Opus configuration, stick to creating context menu items which only apply to Opus -- i.e. set the type drop-down to "Run an Opus Function (not supported in Explorer)" or similar. Those should then stay part of the Opus config without becoming part of the Windows config.
Thanks for the clear explanation Leo. It guided me to an understanding of why restoring settings on another PC did not work for me even though the OXR file was present. The piece of the puzzle that has to be in place on the target is the relevant filetype registration. For anyone who is interested....
[ol][li]Settings --> Filetypes --> System File Types --> New and create a new filetype - e.g. TST[/li][li]Edit the new filetype definition and add standard Opus functions for double click, etc. - e.g. open with Notepad[/li][li]Save and test to confirm that the Opus commands do what they are supposed to[/li][li]Save Opus preferences and restore on target PC[/li][li]Repeat step (1) on the target PC[/li][/ol]
The last step is the bit I had missed. Obvious in hindsight!
The filetype must be defined/known in order to do anything with matching files.
