Same issue as before but solution is to have a 0,1 second break before the left mouseclick.
Amazing, Andreas, it is the first time in decades I am able to control Logic GUI just via keyboard commands. A long christmas wish I had to Apple/ Emagic Hannover which was always ignored Goose bumps!
Newbie question: using a trigger key ("4") - which is needed - but also used when typing in text, can I prevent BTT to fire up this macro? Is there a way to differentiate anyhow maybe? (see video)
Understand, but BTT does not like this. As soon as 4 has to be pressed 1s, all additional BTT shortcuts with modifier+4 will follow this behavior, which they shouldn't as I put the 1s only on the first. BTT seems to save this and recalls it for all shift+4, ctrl+4, cmd+4 etc.
Please see the attached photos from "4" and modifier + "4".
Also:
1.) Forgot to mention, that writing "text 1234" the 4 isn't possible although I am pressing very short.
2.) if the window I am targeting to isn't selected, but I press those new shortcuts, very different unwanted stuff happens which I'd like to prevent BTT doing. For example the App goes in Fullscreen, the main window gets hide in the macOS menu bar at the bottom. This brings in new chaos.
Apologize. We need a German forum for this App by a German developer, Frank /continues joke
I followed your advice and set up 1,43 s minimum holding time to fire this shortcut. Now 2 things are happening:
BTT suddenly saves this 1,43 s for my other action triggers: shift+4 and ctrl+4. Weird.
Writing in a textfield inside the app "test 1234" does not work, the 4 isn't reacting, what I get is "test 123". My understanding of the 1,43 s minimum holding time concept was to prevent this issue, no? But now, neither the action sequence is triggered anymore, nor the "4" can be typed in as text.