Skip to content

Conversation

@unresolvedsymbol
Copy link

Specifically XF86 keys, which are in 0x10080001+ ranges. When these are passed straight to Keyboard::_states[...] = ... it's definitely not good.

Specifically XF86 keys, which are in 0x10080001+ ranges. When these are passed straight to Keyboard::_states[...] = ... it's definitely not good.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant