wlserver: Implement keyboard input filtering #1907
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ction of keyboard keys to clients.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow for subset of keyboard keys to be processed by gamescope, and thus client applications. This commit adds a
--keyboard-filteroption that allows users to specify a subset of keyboard keys to be passed to client applications. This is primarily useful when combined with #1897 allowing for a helper program to pass partial keyboard implementations to each window, but can also be useful in normal operation to avoid mixing keybinds with clients and the main compositor. This option takes a list of values or ranges, including the example of--keyboard-filter 17,30-32,57to pass only the keys wasd and space, although this may not be a usual use case.