StudioNeuneu
12 discussion posts
It doesn't work.
To be sure I didn't make any mistake, I tried with another app, and it worked. So I think Directory Opus doesn't remember on which monitor it was closed...
By the way, I don't like how the trigger work. The app open first in the primary monitor, then it move on the secondary. I would prefer it open directly on the secondary one...
Well, I think I will have to live with it...
Thank for your help.
Ah ok. Directory Opus might be overriding the starting position. You can try adding a "Wait" action to the Trigger rule (make sure to drag it up above the Window Move action) to see if DF can move it a few seconds after the window opens.
It also could be that it's not technically a new window (i.e. if they're reusing window handles). In that case, you could change the Trigger Event to "Window Focused," though that would cause the Trigger to fire every time you switch to the Directory Opus window.
Regarding the short delay before the window gets moved by the trigger, we had to do it this way, because many applications don't like to be moved before the window is fully visible.
Please let me know if you have any other questions at all.
Thanks!
StudioNeuneu
12 discussion posts
Hello !
So I added a "Wait" action with 2000ms then a "Move" action, and it worked.
I deleted the "Wait" action and it worked too...
Now it does what I want (a move then a maximize).
I don't know why it didn't worked last time, maybe I made a mistake, or maybe it is because of the update (DF 8.1 beta). Also when the window move to the secondary screen, it is very fast, not like before, so it's good.
Thank you very much for your help !!!
