Hi,
I’ve configured Caps Lock trigger to Act as Hyperkey (with "do not include shift" enabled).
In the my Aerospace config, I defined distinct shortcuts:
- Ctrl + Cmd + Alt + B
- Ctrl + Cmd + Alt + Shift + B
Issue:
Hyperkey + B works as expected, but Shift + Hyperkey + B (i.e., Shift + Caps Lock + B) is not recognized at all. However, when I press Ctrl + Option + Cmd + Shift + B manually (without using Caps Lock), it triggers correctly.
This seems like a bug in how the Shift modifier is handled when combined with a Hyperkey mapped to Caps Lock.
I used this website to do some test, here is the keyboard events when I press shift + caps lock :
Please note that i disabled all other triggers in BTT except the caps lock to hyper one.
If i configure Hyper Key (still without shift) in Raycast, the behavior is good :
Thanks for looking into this.
Can you check whether it behaves correctly for you in 5.504 alpha (uploading now, available in ~10 min)
1 Like
When I do shift down, caps lock down, caps lock up, shift up, result is the same:
However, if I do caps down, shift down/up, caps up, here is the result:
No Idea wtf is going on with cmd ("Meta" as this website calls it).
This is a test I am not sure I did in the previous version..
Weird, I just tried in a few apps and was able to record and use the hyper key with manually pressed shift fine. I'll check again later!
I'll also test in a clean env to be sure that there is no third party creating unwanted fuckery.
It is also possible that the website records some intermediary event states that BTT might not handle because they are not relevant for shortcut triggering. I'll look into that
Ok it seems to work after having deleted (and not just disabled) all triggers. I think I did a bit too much of copy/cut paste of actions and triggers, it must have corrupted some config because I noticed some other bugs lately (modifying some action having effect on some other actions, UI not updating correctly when changing selected trigger, etc.)
I fixed some UI updating issues recently, did you still encounter them with this alpha?
One I encountered quite often was "create a trigger A, add an action, go to another trigger B, paste the action and edit it" -> I had cases where the action from trigger A was modified. Sometimes both. At least that was what was shown in the UI, underlying data was maybe ok. I never managed to replicate consistant behavior (I did not put many effort to do it) and just deleted and recreated the actions or triggers.
I don't know exactly on which latest alpha it happened, but it absolutely did in the last 2 week.
Ooooh I figured it out. There is a conflict with Supercharge ! The option to "prevent accidental quits" is causing a bug when set to "Hold Command Q".
Here is a video of the issue, where I press Caps Lock with and without Supercharge feature enabled:
Maybe for now configure these in BTT:
1 Like
Thank you, it seems perfect for my usecase.
Unfortunately I encoutered a new bug.
I configured in aerospace shorcuts for HYPER + UP/LEFT/RIGHT/DOWN.
If I use ALT+CTRL+CMD+(arrow) it works.
If I use CAPS_LOCK+(arrow) it doesn't.
Both work with Raycast hyperkey.
Here is the output of CAPS+RIGHT in your event viewer:
Here is the one of ALT+CTRL+CMD+RIGHT:
Difference seems to be only key/modifier in "key state" column.
Does anyone else have this issue with arrow keys?
I had to go back implementing HyperKey with Karabiner.
for special cases like this, configure the shortcuts in BTT and trigger your aerospace actions through BTT. But using Karabiner is definitely also a good option as it can work on a lower level.
In that case I would have to relocate all my aerospace shortcuts in BTT because I don't like the idea of having some here and some there. I prefer to keep separation of concerns and outsource Hyper to Karabiner for now.
Thanks for you usual incredible availability 
