12.1: Problem getting current path from outside Opus

Hi dopus team,

Congrats again for dopus 12 :thumbsup:, wonderful software...

I've just upgraded from 12.0.15 to 12.1 and it introduced a bug

I'm using an autohotkey script to open the current source folder (in dopus) in open/save dialogs...

But since 12.1, when dopus does not have the focus, this part :

Run, C:\Program Files\GPSoftware\Directory Opus\dopusrt.exe /cmd Clipboard SET {sourcepath$}

to get the current source folder, returns nothing...

really strange :open_mouth:

changing /cmd to /acmd make it work again...

I don't think any of the changes from 12.0.15 to 12.1 would have changed how that behaves.

I suspect you just hadn't run into a situation where /acmd was needed until now. Using /acmd is usually the same as using /cmd, except in a few edge cases. Generally, /acmd is the right one to use.

Leo, I litterally use the script hundreds times a day, this behavior is brand new.

Is that an expected behavior that :

Run, C:\Program Files\GPSoftware\Directory Opus\dopusrt.exe /cmd Clipboard SET {sourcepath$}

returns nothing if dopus does not have the focus ?

It works here, from a command prompt, whether or not Opus has focus. (Once I put quotes around the exe path.)

Have you got any empty folder tabs open? Or tabs showing something that doesn't have a real path? (e.g. The Computer folder.) The /cmd is probably being routed to a tab that cannot generate {sourcepath$}.

no empty folder tab, no tabs showing something that doesn't have a real path...

i use the script in open/save dialogs so dopus does not have the focus...

works with acmd, does not work with cmd

and DID work with cmd before...

Here's what I see:

leo.dopus.com/posts/dopusrt_cmd_ ... rd_set.mp4

I totally believed you :wink:

Here's what I see:
dropbox.com/s/r0ph65gta8d7h ... g.wmv?dl=0

Maybe there is a strange/voodoo thing happening on my pc...

The video doesn't show which listers and tabs you have open.

There was only one lister with two tabs (C:/ in source) and (C:/Dropbox in destination)

Anyways, this morning, after a full shutdown...it seems that my computer is behaving normally again...
because i cannot reproduce this bug :thumbsup:

i would like to know what happened, but i guess it will stays a mystery :smiley:

I've changed /cmd to /acmd :wink: