Page 1 of 1

Feature Request: display which plugin in statusbar

Posted: 01.05.2015, 02:52
by BGM
When testing the lister plugins, I want to know which plugin actuallly gets used.
Right now you have to guess.

I propose that the name of the plugin that gets used be displayed in the statusbar.

Also, it might be nice to add a button that lets you cycle through plugins. Right now only the first match gets used, but if you want to try a different plugin you have to go and disable the one that gets used and then try again. A buttin to cycle plugins could be useful in testing.

Re: Feature Request: display which plugin in statusbar

Posted: 01.05.2015, 08:39
by Timon
Brilliant idea!

It would be nice to do something similar for Archiver plugins (for Unpack... and Copy to/from archive) -
Also, it might be nice to add a button that lets you cycle through plugins. Right now only the first match gets used, but if you want to try a different plugin you have to go and disable the one that gets used and then try again. A buttin to cycle plugins could be useful in testing.
While Pack.. we can select archive format, but we can't be sure what plugin is used.

In case of Archiver plugins, first matched plugin can give error message while unpacking, and we have to make many unnecessary actions to use another plugin for the same file type.

Re: Feature Request: display which plugin in statusbar

Posted: 06.05.2015, 13:51
by uwee
If you enable the option [general] - [document title] "show title bar" of the quickviewer you will see exactly what you want :)

Re: Feature Request: display which plugin in statusbar

Posted: 06.05.2015, 14:50
by joby_toss
Image

Image

Re: Feature Request: display which plugin in statusbar

Posted: 06.05.2015, 15:42
by BGM
Joby, well, that sort of works - but it's a nice idea!
Problems:
If your viewer uses the internal viewer, the title bar caption is the file name, not "internal viewer".
Also, if you switch between image/text/rtf/plugin on the viewer's toolbar, the caption does not change. (I tried with a txt file)
Also, sometimes if a plugin receives the chance to offer a view, but isn't able to read it, you just get a blank panel with a filename. You can't see which plugin is trying to work.
It's not foolproof, anyway.