I was pleased to find this thread from way back in 2005 and managed to get both .DIS and .XPI archives to behave the same as .ZIP archives. Specifically, I want to use Ctrl-Double Click to open in dual and Shift-Double Click to open in a new lister. In order to achieve this, I had to follow Jeff Stewart's instructions and add specific file type entries for DIS and XPI. Two things struck me about this:
[ol][li]When a file type is added to the list of ZIP equivalent extensions in Preferences --> Zip Files --> Settings, why not treat it exactly the same as ZIP unless there is a separate overriding file type definition? Having to create a specific file type definition in order to duplicate ZIP actions seems to me to be the wrong way round.[/li][li]When copying an existing file type (e.g. ZIP) in order to create a new file type (e.g. XPI) it would be good if the associated event definitions were duplicated as well, to save having to recreate them all manually for the new file type.[/li][/ol]Regards, AB
And going back to that old thread - I think what was happening to those of use who were NOT seeing the same results as Steve (Tanis), was that we did indeed have "File Type" associations with these other file extensions we were adding which were overriding the mouse event behavior... You certainly don't have to create a "new" file type association - you could just modify any existing association for that extension to run Opus "Go" pr whatever... but not sure if you'd always want to do that, or have Opus automatically do that. For instance, if you have a "zip" file format with another extension that just so happens to be associated with some other archive app like PowerArchiver or 7-zip or something that ALSO supports other types of archives that Opus does NOT support (like 7z files). In that case, you might not want to modify a file type that includes a bunch of other extensions that an Opus "Go" command wouldn't work on - right? The reality is that lots of the archive apps out there actually register file format specific file types nowadays (like separate file type entries for Winzip "zip" file vs Winzip "cab" file vs Winzip "arj" file, etc) so it's highly probable that what I just said wouldn't actually happen... but again, it's an example of why you might not want Opus to go out there and automatically modify existing file type associated events in a case like this - adding extensions to Opus' list of Zip files.
I suppose you could still request that GPSoft add some sort of option so that it automatically goes out and updates whatever file types you add to the list of zip files such that events and actions that you've already got configured for something specific in Opus (perhaps just for the "ZIP" file type - or maybe even an Opus specific "Supported Archives" FileType Group or something) gets applied to the newly added file extensions file type association - just so that you have consistency in behavior with the existing and newly added extensions; though if it did it that way you could still have consistency get messed up depending on how you later make your own "changes" to things.
Personally, I'd prefer Opus to NOT actually go out and modify a bunch of other application specific file type associations, and would rather know if there's some way that we could check a box or something so that Opus would internally re-prioritize certain things (like the variations on double-click events) to take precedence from something defined in an Opus specific area like a FileType Group - as opposed to the more file specific type association which usually takes precedence...
If that could be done, you could even change out your third-party archive app altogether (say, from WinZIP to PeaZIP or something) and not have the behavior configured specifically in "Opus" experience any change at all, which would otherwise require you to at least go back to each 'new' app specific file type and re-update the individual file type associations to run the Opus "Go" command an what-not instead of whatever the new app lays down.
Does any of this make sense?
Depending on how/where you configure certain things (and this is really a Windows file type system issue, and not an Opus issue) you can experience similar havoc with media file formats when you start installing and trying out other media apps. Yikes... it's not Opus' fault at all, but it would be kind of nice if Opus could provide a way to sort of "insulate" us from changes made by other apps, so that behavior from Opus would remain consistent with what you want to happen normally. But I'm a bit jaded from the perspective that most of the "havoc" I'm talking about may not be experienced from "most" users - but for those of us who routinely "try out" new apps, maybe you see these sort of things happen more often.