QuickView doesn't respect higher priority of associated plugin

[DrShark]

For me this issue is reproduced with 2 plugins installed: 1st with higher priority is associated with some extensions, 2nd with lower priority doesn't have associations defined in wincmd.ini, but is able to handle file types associated with 1st plugin. In below reproduce steps I'll use plugins I have installed:
1. Install lister plugins like that:

Code: Select all

[ListerPlugins]
0=c:\totalcmd\Plugins\wlx\CudaLister\cudalister.wlx
0_detect="EXT="MD" | EXT="TS""
1=%COMMANDER_PATH%\Plugins\wlx\ulister\ulister.wlx

2. In some folder, place *.ts and *.js files.
3. Open .ts file using Ctrl+Q: QuickView will open it in CudaLister plugin, which has higher priority for this file type.
4. Move file cursor using up/down keys or mouse to .js file: QuickView will use ulister plugin to show it.
5. Move cursor back to .ts file: QuickView will still use ulister which has lower priority.

[petermad]

I cannot find where, but I am sure Ghisler has said that this beheaviour is on purpose. It is not a matter of priority, but it is that the currently used plugin is used when changing to a new file, if that filetype is supported by the current plugin.

The idea is that you can press Ctrl+Q on a file, then click on the Quick View panel and press 4 to switch to the another plugin that can show the file, and thereafter this plugin will be used for the next files, as long as the filetype is supported by that plugin.

[ghisler(Author)]

That's exactly the reason! The filters are only used when
1. Opening the lister or quick view
2. Switching from one of the other modes to '4'

[DrShark]

I knew similar thing happens with QuickView behavior for text view e.g. in case it can't detect ANSI or ASCII encoding, Christian Ghisler described this in email reply to one of my reports about difference of Lister and QuickView behavior:

[... if QuickView] cannot distinguish between manual OEM mode (the user has set it) and auto-detect OEM mode [...] when you switch to the next file and [QuickView] is in OEM mode, it will remain in OEM mode because it assumes that the user wants to view files in OEM mode.

I didn't expect similar behavior in QuickView exists for plugins too...

I suggest to introduce new cm_<somename> command with parameter to control QuickView behavior, and suggest at least following values for parameter:
0 - current QuickView behavior, it will decide what mode to use for text and what plugins to use in Multimedia mode.
1 - Use Lister behavior to decide what mode to use for text, but QuickView method for using plugins.
2 - Use QuickView behavior to decide what mode to use for text, but Lister method for using plugins.
3 - always use Lister's method to decide what mode to use for text and what plugins to use in Multimedia mode.

I'm talking not only about wincmd.ini parameter, but about cm_ command because QuickView is used to view many files quickly, and user may have a need to change QuickView method of work quicky without TC restart.