Viewer settings in search
Viewer settings in search
Using v. 664 64-bit.
I have several programs set to replace the internal viewer for various file types. In the main file panes this works as expected -- the correct viewer is loaded for the correct file extension. But in the Search Files/Folders panel, when I select viewer for a file that has been found, FC always uses the internal viewer. Is this a bug? Or do I need to set something to have this work?
I have several programs set to replace the internal viewer for various file types. In the main file panes this works as expected -- the correct viewer is loaded for the correct file extension. But in the Search Files/Folders panel, when I select viewer for a file that has been found, FC always uses the internal viewer. Is this a bug? Or do I need to set something to have this work?
Re: Viewer settings in search
In Configure viewer -> Plugins (F3 then F9) see if your plugin path is correct.
After installing a plugin it's better to save the settings and then restart freecommander, I think...
After installing a plugin it's better to save the settings and then restart freecommander, I think...
Re: Viewer settings in search
If you are talking about this setting, you're right, it doesn't "stick" for the search window, but it's not an x64-only bug:
Re: Viewer settings in search
Yes. The programs I have there work in the regular file pane, but in search the internal viewer comes up. The programs I have in the Editors tab do work properly both in the regular file pane and in search.
I hope this is something that will be fixed at some point.
I hope this is something that will be fixed at some point.
Re: Viewer settings in search
It works fine for me for Viewer (F3) and Quick Viewer (Ctrl+Q) in the search dialog.
Re: Viewer settings in search
Marek, I've sent you a PM with a small video demo. Thanks!
Re: Viewer settings in search
Are you having the same problem?
Re: Viewer settings in search
It's not a problem for me because I don't use that option, but yes, it does happen to me and yes, I believe it's a bug (for both x86 and x64 versions).
EDIT: Fixed in build 666. Thanks!
EDIT: Fixed in build 666. Thanks!
Who is online
Users browsing this forum: No registered users and 161 guests