-
-
Notifications
You must be signed in to change notification settings - Fork 848
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
Consumer keycodes for launchpad and mission control are unknown #3310
Comments
I join |
Same issue on the Keychron K6 Pro, they are registered as unknown events and not passed on. |
Keychron Q1 Pro, exactly same
|
@tekezo how about add these ID into https://github.com/pqrs-org/cpp-hid/blob/dbfe730bbe353ef5ea86b6a2bbd03748af0be9c0/include/pqrs/hid/usage.hpp#L300 ? |
Would adding this be enough to make it work? 🤷🏼♂️
|
any progress on this? or a workaround? I have a Keychron Q3 and the same issue. |
I'm having the same issue. Those two commands don't work with Karabiner running. Keychron K8 Pro. |
Same issue here. |
Same issue with Keychron B1 Pro.
|
I have a Keychron K8 Pro keyboard, and noticed that, when Karabiner-Elements was modifying events for it, the Launchpad and Mission Control keys didn't work. This keyboard sends consumer keycodes (usage page 12) for these buttons, and the other consumer keycodes that this keyboard sends, in particular brightness, play/pause, next and previous song, and volume control keys, are all recognised by Karabiner; they're correctly identified in the Karabiner-EventViewer, and when event modification is enabled they work as expected.
Here's the JSON output of the Unknown Events tab in Karabiner-EventViewer, showing the keycodes being used. The first key pressed is the Mission Control key, and the second is the Launchpad key.
These keycodes are correctly recognised by MacOS and do what I expect. Can they be added to the known events in Karabiner so it passes them through correctly to the virtual keyboard?
The text was updated successfully, but these errors were encountered: