Physical Modifier Key Press Required After First Press.

I am running into a problem where a physical modifier key press is required. I’ve used multiple AI chats to experiment solutions, but no matter what I try, the only way to make it work is by physically pressing the keyboard.

For specifics, I am trying to trigger the Launchy App (which requires only held modifier combinations to trigger, Option+Command by default). My current approach is to trigger this with a Magic Mouse 3-finger click over the menubar, which I can do the first time. However, all subsequent attempts fail UNTIL I physically press any modifier key. Then it works again.

My ultimate goal is a 3-finger click and hold (press command and option), and release click releases the option command. Without needing to reset the modifier keys physically.

Thanks in advance! I’ve spent entirely too much tine on this and am happy to pay you to solve it :slight_smile:

Here is a VIDEO

Best,Craig

I have also found that it can be difficult to release the modifiers (Pressing always works). Sometimes these “techniques” work. The release command is given several times in a row with short pauses in between. Unfortunately, though, there’s no guarantee that this will work.

Understood. Thanks for the response.

So I did a lot of testing yesterday. The problem is that there are multiple ways to detect modifier key presses for apps like in your case Launchy. Unfortunately producing modifier key events programatically is complex and I have not found any way to produce exactly the same events as pressing the real keyboard modifier keys produce programatically.

However I can produce events that will work for various situations. With 6.375 I have added a new predefined action "Set / Press / Release Selected Modifier Keys" that offers various options that should make every use case possible.

For launchy this seems to work well:
Press:

Release:

Great, thank you Andreas. This seems to be a significant improvement :smiley: :clap:

Thanks so much for the extra effort. Once I set my mind on a certain workflow, I find it hard to stop myself and have spent a lot of time on this one myself. :nerd_face::rofl: May I have access to 6.375 to test?
Thanks! Craig

it is available via alpha update already! (or https://folivora.ai/releases/btt6.376-2026041402.zip )

That works well! I am still running into the problem of needing to periodically reset with a manual key entry, but this new predefined action opens up many new possibilities :slight_smile: Thanks again

@Andreas_Hegenberg Am I understanding this correctly: This setting should press the r opt key.

And this setting should release the r opt key.

If that doesn't work, does that mean I'm supposed to try all these options in every possible combination?

depends, what are you trying to do? It’s mostly for external apps that need to recognize modifier keys, depending on how the other app tries to recognize modifiers, different settings will be required

I'm trying to do something really simple... at least in my head :slight_smile:

Press and hold “F” for a longer time = press and hold “r opt”.

Release “F” = release “r opt”.

While “F” is pressed and held, the shortcut “r opt + P” set up in BTT should be triggered.

So here it's F + P.

that is the opposite of simple :joy:
But I think I can add an option to make this work as well. I’ll check later!

That already worked with the old virtual modifiers—I mean triggering F (r opt) + P. So, no magic.:smirking_face:

What didn't work was reliably releasing the modifiers.

Right now, nothing works at all :joy:

Tell me, unlike pressing and releasing modifiers, blocking and unblocking the keyboard always works quickly and without any issues. Does that have to do with it being a separate BTT function?

blocking keyboard is easy, modifiers are really complex and the system API‘s contradict each other because they are not made for this kind of stuff - we are interfering a lot with what the system thinks the modifier’s state should be

I see. Then I’d like you to fix the issue with key repetition when the keyboard is blocked.

This one. Key repeat is important for navigating in a text.

And: This “F” thing is called Homerow. That means keys your fingers are already resting on can be used for different things.

You can set that up really well with BTT (block/unblock the keyboard). Even pressing two letters at the same time (as two modifiers) and then a third to trigger something works perfectly. And more than that. It took me a while to solve all the problems. But now I’m ready.

As soon as you’ve solved the problem above, I’ll post a preset for everyone. I’m surely not the only keyboard fan here. Or am I? :joy:

Will you solve the problem mentioned above? :slightly_smiling_face: :folded_hands:

not what you want yet, but 6.379 adds a new option for keyboard shortcuts that lets you pass through the original key/shortcut if the advanced trigger conditions fail:

This will allow you to get rid of the J=J shortcut

Hmm, ingenious. And it seems to work well :slight_smile: Thanks!

The only thing missing now is key repeat for the arrow key. Do you think you can handle that too?

Edit: Ah, wait, now I get it, that problem is solved too.