Focus on other already running program
Posted: Sun Aug 13, 2023 11:24 am
Not so much a technical issue, but a key option or function that seems to be omitted.
Let's say I have 3 programs running: A, B and C, and I perform some Mouse button 4 and or 5 actions in B.
Now after that I want to shift focus to A or C, which I can achieve easily by including the {alt}{tab} with or without {shift} as the last instruction.
That works fine.
But if I want to go directly to A or C, I can't.
Because here is the situation:
If I have opened more program(s) (e.g. D, E, F.), that "handing over control to ..." last instruction isn't working anymore as intended.
Because, obviously, if I go from D to B, the {alt}{tab} in Mouse button 4 won't take me to A, but back to D.
Now I thought that the ACTIVATE would do the trick, but that's not the case. It's depending on where the cursor is (which is still in B).
The RUN:<application> starts a NEW event, and does not Activate or focus the already running one.
THAT is what i'm looking for.
Am I missing or misunderstanding something, or is simply not programmable?
To me this seems to be an enormous (automation) addition to the workflow.
Kind regards,
Sydney
(Amsterdam)
V2.20.5 / Installed / Windows 11 / 64 / Intel i9 /32G Ram (quite state of the art...)
Let's say I have 3 programs running: A, B and C, and I perform some Mouse button 4 and or 5 actions in B.
Now after that I want to shift focus to A or C, which I can achieve easily by including the {alt}{tab} with or without {shift} as the last instruction.
That works fine.
But if I want to go directly to A or C, I can't.
Because here is the situation:
If I have opened more program(s) (e.g. D, E, F.), that "handing over control to ..." last instruction isn't working anymore as intended.
Because, obviously, if I go from D to B, the {alt}{tab} in Mouse button 4 won't take me to A, but back to D.
Now I thought that the ACTIVATE would do the trick, but that's not the case. It's depending on where the cursor is (which is still in B).
The RUN:<application> starts a NEW event, and does not Activate or focus the already running one.
THAT is what i'm looking for.
Am I missing or misunderstanding something, or is simply not programmable?
To me this seems to be an enormous (automation) addition to the workflow.
Kind regards,
Sydney
(Amsterdam)
V2.20.5 / Installed / Windows 11 / 64 / Intel i9 /32G Ram (quite state of the art...)