would you mind showing a screenshot? I can't find that in settings.
If I have Caps Lock remapped to Right Ctrl in the system settings, can I set up a shortcut in BTT to bring back the original Caps Lock function in case I need it?
When I set up a shortcut and select "Toggle Caps Lock On/Off" as the action, it doesn't do anything. It used to work when I had Caps Lock remapped as a Hyper Key. Any ideas?
when it‘s remapped there is basically no more caps lock, so this is not possible anymore then
Ah, so this workaround isn’t 100% functional either. My native language is Czech, and we use an extended Latin alphabet with additional diacritics like ĚŠČŤŽÝÁÍÉÚŮ, which are typed using Shift+2/3/etc. For longer texts that I want in uppercase, it’s going to be inconvenient without Caps Lock. I guess I’ll have to write a script that converts selected lowercase text into uppercase.
Thank you anyway. Your quick support is amazing.
you could maybe solve that using the "shift key down" and "shift key up" actions
It won't work. I mixed up the description. What is the symbol for 2 on a US keyboard, on a Czech keyboard it types the character ě by default. With Shift, it types S. With Caps Lock, it types Ě. That's why the key down/up operation won't work.
If you have some other key to spare, you could remap that to caps lock (https://hidutil-generator.netlify.app )
I don't have a free key on the internal keyboard. I do have one on the external keyboard, but I don't want to rely on that because I don't have it with me when traveling with the MacBook. Do you think it would be possible to set Caps Lock to something like F13 and then create a shortcut in BTT that behaves as F13? Or do the keys in HIDutils need to be physically present?
In 4.957 alpha (uploading) I have completely rewritten the hyperkey functionality. It should solve the LED issue and work with third party apps. If this works well I can also extend it to other keys.
Wow, you're fast! How "stable" are BTT's alpha versions? I'd like to try out and test the feature to give you feedback, but it's on my work computer where I can't afford any issues.
If any potential bugs only affect BTT's behavior, I'm okay with tolerating that. However, I’d rather not have it impact other applications or the system itself.
I think the worst that can happen with this version is that it breaks your capslock key, but that can be reset if necessary
what do you mean by capslock key break? btw, for me hyperkey works like "hyperkey app", all my shortcuts are working + no green light
Thank you dev
well, BTT now calls some function to temporarily disable the capslock key - if BTT is quit without enabling the capslock key again it will not work until you start BTT again. I‘ll improve that soon.
Hi,
I just tested the new hyperkey functionality. It works great (nice!), but BTT does not seem to take "Advanced conditions" into account on it in my setting. What I am trying to achieve is to let Capslock be used as a hyperkey or not according to the value a variable that is set by means of a key sequence.
A few details:
- BTT 4.959 / Ventura 13.7.1 (a bit old maybe)
- I have checked that the result of the condition I have set is "currently false", but the hyperkey is still active
- I have tried to reboot both BTT and my mac
@odapg Yes, this is not yet implemented. However if the approach in general works, then it will be easy for me to extend it with conditions etc.
Maybe what you want can already be achieved with the named trigger option (I think the named trigger can have conditions already ):
Yes, that works!
Thank you very much, that's really great!
So I gave it a try, and it seems to be working. When I initially set up Caps Lock as the Hyper Key, it got stuck in the "on" state, and the shortcut didn’t work. However, after resetting it in the system settings, everything is running smoothly now. The LED doesn't flicker, Hyper Key shortcuts work on the first try, and I can reliably use another shortcut as a Toggle Caps Lock if I ever need it. Hopefully, nothing else breaks. Thanks again.
Sounds very promising so far! Thanks for testing!
Hmm, I might have spoken too soon. The LED doesn't flicker as it used to, but I've already noticed twice that the Hyper Key only responded on the second attempt. I can't figure out how to replicate the issue. It usually happens if BTT isn't used for a few dozen minutes, or maybe just if Hyper Key shortcuts aren’t used. Hard to say since the shortcuts I use most are mapped to it.
Is there any log in BTT that tracks recent key events that could help analyze what’s happening? Feedback based on "feelings" isn't exactly ideal.