Implement keyboard-shortcuts-inhibitor-v1 #1969
Merged
Conversation
This file contains 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
Closed
ammen99
force-pushed
the
add-shortcuts-inhibit
branch
from
5e10dce
to
ac93706
Compare
|
It works fine, thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Supersedes #1372
Thanks to @lilydjwg for doing the initial work, it was certainly helpful :)
Fixes #1171
This PR adds support for the keyboard-shortcuts-inhibit-v1 protocol via the new
shortcuts-inhibitplugin.I have also added a few nice-to-have functions:
shortcuts-inhibit/inhibit_by_defaultset toapp_id is "wlroots"so that nested Wayfire can use the same shortcuts as the host.shortcuts-inhibit/break_grabset to<ctrl> <alt> KEY_ESC(disabled by default though).It would be nice if someone else could also test and verify that this works. I have only checked the wlroots example.