- I wan to replace (⌘ Space) search key that is present on a generic keyboard to option key! Can't figure it out how to do that without tampering with actual spotlight hotkey!
- Also I changed right control to right option but when I kept holding that option (
for antinote, it only trigger antinote once and then again have to click ⌥ key to trigger again ( this is not the case with karabiner or default) how can I fix it?
what kind of keyboard is it? Question is whether it is a standard key that can be remapped or whether it is some special function of the keyboard that just sends cmd+space
How did you change right ctrl to right option? If you use the low level key remap like this, it will behave like a real option key - apps are not able to see any difference and can not behave differently then.
I remapped prnt scrn key which send ⇧ ⌘ 3 to ⇧ ⌘ 2 via key sequence and can do so for search key too but I want to make it option key (right) but it is not happening. (I think its some special keys- on Mac mode send cmd + space and on windows mode send other keys.)
-
I was choosing keyboard but leaving that empty also not solve it for me, antinote app want me press that ⌥ key twice- which is not the case when I do it via karabiner. (⌥ + ; to show antinote, and without leaving ⌥ key pressing ; does nothing)
[
{
"BTTLastUpdatedAt" : 1783807042.6279459,
"BTTTriggerType" : 805,
"BTTTriggerTypeDescriptionReadOnly" : "Remap Keyboard Key: right_control => right_option",
"BTTTriggerClass" : "BTTTriggerTypeOtherTriggers",
"BTTUUID" : "E3E36298-28D8-455F-8CBB-95526FB83192",
"BTTShortcutToSend" : "30064771300",
"BTTKeyRemapFromKey" : "30064771300",
"BTTKeyRemapToKey" : "30064771302",
"BTTOrder" : 5,
"BTTTriggerLauncherConfig" : {
"BTTLauncherShowInLauncher" : 0
}
}
]
here's karabiner do without issue
there are few issue I think in the latest alpha:
-
the remapping right command to right option not working correctly- like I assigned ⌥ L for calendar to show/ hide so hold ⌥ press L once to show and again to hide but that won't happening
-
I am trying to make the search key that parse ⌘ ⇧ F23 to option key via key sequence by action set exactly these modifier to option but it keep holding option key always- other action like mission control has no such issue
if you have karabiner running or even installed at the same time as BTT, that will cause issues with the low level remapping.
Apart from that your remapping config looks fine and will definitely work, this is basically just passed to the system. Once remapped the right ctrl key will be a right option key, the rest is handled entirely by the system.
As you said, I unistalled karabiner, restarted device but still the same issue- you can check that on your device too just assign any key like g, h to right option and try pressing twice any shortcut command
I have ⌥ L for calendar to show / hide app but it won't work with it @Andreas_Hegenberg
@Andreas_Hegenberg tried turning on "always use old keyboard shortcut implementation" and now right control succesfully remapped to right option, does using old keyboard shortcut implementation has any quirk?
but still the spotlight key which assigned for F23, on remapping that to right option, the problem still there! even the old keyboard shortcut is not fixing that
Also, I am trying the key sequence, 'h' key down for option key holding so can use as modifier and 'h' key up to release all modifier but even on releasing ⌥ key is being kept held and alternate character being pressed
old keyboard implementation is irrelevant for key remapping! (basically never enable the always use old keyboard shortcut option, it is only there for legacy reasons)
For key sequences etc. things get very complicated if you want to trigger a modifier key. You will need to experiment wtih the various options in the modifier key action to make it work for your use case. Different apps might behave differently there.
The only really reliable way to remap keys to modifiers is via the „remap key“ functionality
There might be a workaround for this. It sounds more complicated than it is.
“h” down --> Blocks the keyboard
‘h’ up --> Resets the keyboard to normal and types “h”.
Now you set up: When the keyboard is blocked, then, for example, “o” = opt + o.
So if you now type h + o, opt + o is triggered.
I think this works, but it also has some drawbacks.