-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Function keys not working on OSX #172
Comments
Please check if comments on #120 have anything useful. |
Thanks for reporting. I will try to reproduce it soon. |
Thanks for the link to the previous issue involving functions keys! I tried to remapping the function keys but had partial success as I had to press the fn key to access the "multimedia" keys, and the mapping was wrong, ie, mute mapped to vol down, vol down mapped to vol up, and vol up still does nothing. I guess that the keyboard (logitech K380) itself does some "mapping" because even using the event viewer from karabiner i cannot see the "fn" event. F12 maps to "consumer_key_code": "volume decrement" or to F12 if fn key is pressed too. The next key is kind weird, because it shows "consumer_key_code": "volume increment" (keycode 0x00E9) or Lcontrol + Spacebar if Fn key is pressed. It seems that 0x00E9 is not mapped in key.h. Please, let me know how I can help/test this mapping. |
Hi all,
It seems that functions keys are not working or being misinterpreted by keymapper. At first I noticed that the volume keys are not working. Investigating further and using keymapperctl --next-key-info, I'm getting this:
volume up (without pressing fn): nothing
volume up (pressing fn)
key_name = 'Space'
scan_code = 0x002C
system = 'MacOS'
class = 'kitty'
path = '/Applications/kitty.app/Contents/MacOS/kitty'
device = 'Keyboard K380
volume down (without pressing fn): nothing
volume down (pressing fn):
key_name = 'F12'
scan_code = 0x0045
system = 'MacOS'
class = 'kitty'
path = '/Applications/kitty.app/Contents/MacOS/kitty'
device = 'Keyboard K380
F5 (without pressing fn):
key_name = 'ArrowUp'
scan_code = 0x0052
F5 (pressing fn):
key_name = 'F5'
scan_code = 0x003E
So, some keys looks ok, but most not. I'm running keymapperctl 4.6.0, slight modified to ignore the mx anywhere 2s mouse.
The text was updated successfully, but these errors were encountered: