i used to use the following commands to open selected files with various software...
Notepad.exe {filepath}
or
"C:\Program Files\Notepad++\notepad++.exe" "%1"
or
C:\Program Files\Adobe\Adobe Dreamweaver CS3\Dreamweaver.exe "%1"
if the program is not opened it does not work as expected... only the first file is opened
and a dopus dialog stays opened forever... see capture below
if the program is already opened, then it works as expected...
i'm sure it was working at some point... i don't know when this bug appeared
%1 only sends one filename to the program at a time.
If several filenames are selected then Opus will run the program once with each filename. It is then up to the program how things work. Opus waits for each run of the program to either exit, or run in the background. It's up to the program whether it ties up the thing that ran it (Opus) until it is exited or whether it runs in the background. In your example it looks like Notepad++ isn't running in the background since Opus's progress dialog indicates it's waiting until it sends the next file.
How you fix this depends on Notepad++. Some programs let you give them multiple filenames on a single line, e.g. using {allfilepath} or %* instead of %1. (%* will work in Explorer as well, if that matters to you. Apart from that, %* and {allfilepath} do the same thing in Opus.)
Some programs let you run them multiple times and send each additional filename to the first instance of the program, in which case you might get what you need by adding @async to the start of the line to tell Opus not to wait. (I think @async does that anyway; I may be wrong.)
Some programs require DDE to be used. (DDE is an old-fashioned way of running programs which makes it easy to have only one instance of them no matter how many files are passed to them.) Opus also supports DDE but exactly which DDE commands need sending depends on the program you are sending them to.
it WORKED for months (i've had this toolbar for more than a year starting with dopus 8)
so something in dopus changed... well that's how i interpreted it...
however i added @async at the beginning and it is now working !!
thanks a million ![/quote]
I don't know/remember the details, but I think I vaguely remember some change regarding whether programs running synchronously or asynchronously is the default.
