Custom Query (518 matches)

If an external program (ie a viewer) fails to run FM2 should generate an error message and ideally preform the function with an internal program (ie viewer) if available

Just checked Filestar's drag and drop and it appears to have none of the issues FM/2 has. It appears that the command options window that comes up in FM/2 causes the delay. Since drag and drop involves no command option window in Filestar, there appears to be no delay. Filestar's drag and drop follows the default setting for drag and drop.

Jim's response was this:

I agree with the above except when dragging the unzip exe file out of the ftp directory with FS/2, there is a delay presenting the dragged icon which locks up the FS/2 clock but not the system clock. When the FM/2 options window appears, the system clock locks for the delay and any/every file(s) seem to lock it up. And the FM/2 delay is considerably longer than the delay presenting the icon for an exe file in FS/2 D&D. The two delays are probably not related, me thinks. I smell a threading issue, the FM/2 options dialog proc must be running on the main thread. In FS/2 most, if not all, functions/dialogs are executed in an object window on a separate thread. However the drag op - up to the drop - is done on the main thread.