I assigned caps lock to hyper key, and then the whole 4keys+Q to lauch an app.
However sometimes it seems that caps lock takes over (have that blue arrow up thingie showing up) and takes 2-3 presses to get the combo working - I can't figure out what's going on.
Help anyone?
Hi @xboh,
Check the following - Hyperkey w/ Caps Lock - doesn't seem to register Hyperkey + other key combos - #2 by xidiot
Yeah, I think I get the config right.. And it's not that it doesn't work, it doesn't seem to work the first time around - and the mac makes that sound like when a wrong key (or unassigned key) is pressed. And then 2nd or 3rd time it works.
Could you please check if when pressed the 1st time (the non-working time) it is being shown under the "Recently Used":
2 (on the screenshot) will be hyperkey+5 for example in your case.
So it seems that the first time it misses the Q (red arrow), tho it still recognizes it as a hyper key.
The second time it picks up the full shortcut - green arrow.
i will add some more debug logs specifically for hyperkey.
If you can already reproduce the issue easily it would be great if you could go to Help => Export Diagnostic Debug Information and send the result to andreas@folivora.ai
I have tried to reproduce, but it always seems to work fine on my machine.
The two triggers appearing in Recently Used is fine.
I think the problem is that SOMETIMES when I press caps lock it recognizes it as a hyper key but allows it to play out ALONE; i.e. the moment i press Caps it shows as hyper key in the recent shortcuts and the next button pressed (even tho the caps is still pressed) is ignored.
It happens often enough, but not consistently.
So something somewhere should tell it - never recognize hyper key alone - always wait for the next key to be pressed with it.
It always needs to recognize the hyper key alone, otherwise it would trigger caps lock. (as soon as caps lock is pressed it will always trigger the hyper key trigger)
alright then, I'll see if I can catch some logs next time it misbehaves.
This is not the issue, because if you check on my screenshot the 1st recognized shortcut is also the same like for your which is to be expected due to the the following config:
I think I had the same issue as you. The solution is either to use a different app for the hyperkey or remap Caps Lock to Right Control and build your shortcuts in BTT around that. That’s what I did, and so far, it seems reliable.
Following as I have the same issue. First key press of BTT-instituted hyper key does not work - have to click it multiple times for it to activate.
