packer plugin switcher

[chrizoo]

-
I didn't want to belittle your solution. Not at all. Sorry if it came across that way. I rather asked to check if I understood the scope of it.

I still don't understand how "two" can cover "several different" packer plugins? (quotes from your last post)

[HolgerK]

Uups, just want to explain in detail how it could work, and mentioned that it already works(under certain circumstances)

Okay. Let's assume you have three plugins that can be used to open a msi file:
Total7Zip
MSI Plus
NTFS-Streams
Only the msi plugin is registered for the extension msi.

Preparation:
- Define an "Internal association" for "*.msi *.msi2"

- Open command ** (default for system association)

- Add a [New] action:
Verb: Open with 7Zip-plugin
Command: **7z

- Add a [New] action:
Verb: Open with MSI-plugin
Command: **msi

- Add a [New] action:
Verb: Open with NTFS-Streams-plugin
Command: **stream

Now open the context menu of a "*.msi" file.
You will see three entries:
"Open with 7Zip-plugin"
"Open with MSI-plugin"
"Open with NTFS-Stream-plugin"

But no matter which of them you select, the file will always be opened using the msi-Plugin.

Now do the same with a msi file renamed into "*.msi2".
Everything works as expected and the file can be opened using three different packer plugins.

It looks like

**ext Use packer plugin defined for extension "ext" to view contents of file

only works for file extensions which are not already registered by a packer plugin.

2ghisler(Author)
Bug or by design?

Regards
Holger

[chrizoo]

-
ok, thank you for the extra explanation and sorry that I misunderstood you

[billiebub]

HolgerK i just tried your way and sure it works. This is great and works like a charm. Sorry for not understanding your initial post about the internal associations. cheers