I don't understand why this Key Sequence
triggers this
because the second one is included in the first one and finishes earlier 
To prevent this you can either use the "Min pause before first keystroke" option on the second one, or the "Trigger only if no further keyboard input is recognized for" (also on the second one)
Yes, that works, thank you 
But I don't understand it. Also in the case below, one sequence is contained in the other but it still works without a pause. 
In addition: “e” and double “e” also work as a key sequence with the advanced conditions. Type “e” when ⌘ is currently down. However, this does not work with left shift.
Anyway, what I wanted to do works. I don't have to understand everything.
For these cmd+e sequences, by default without any further settings the first one would/should always trigger
The cmd+e+e would only ever trigger if you have the "only trigger if no further keyboard input is recognized for X" option is enabled on the cmd+e sequence.
yep, but then it's a different case because the first one is not included in the second one
⌘+E is not included in ⌘+E+E?
cmd_down + e_down + e_up + cmd_up is not included in cmd_down + e_down + e_up + e_down + e_up + cmd_up
That's because the second one doesn't have the cmd_up after the first e_up
It's easier to understand if you do it with lowercase letter for key down and upper case for key up:
⌘+e+E+⌘ is not included in
⌘+e+E+e+E+⌘
Ah, now I understand! At least I think so ...
To be on the safe side, I'll take a week off to analyze this in peace and quiet.
Thank you, Andreas
haha, have a nice week off!
Thank you, my week off was wonderful. And now that I'm back, I realize this.
The KS above is set up for all apps and specific for app A. Since app specific setup usually has priority, the exception should apply to app A. But it doesn't. Unfortunately, the action for all apps is also triggered in app A.
If I remember correctly, you once explained to me that “app specific” before “all apps” does not apply to KS. Just as there is no conflict menu for KS, there is probably also no differentiation between apps. Is that correct?
if it is exactly the same sequence (best copied into the app via cmd+c / cmd+v), then the app specific one will override the global one.
It is exactly the same KS (copy/paste). But the app specific is not triggered.
But wait, the problem arises elsewhere. The app specific KS needs the option “Min pause before first keystroke”, because otherwise it collides with another right shift trigger only.... Now it works. 
God, this is complicated. I need another week off. 
1 Like