Skip to content
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

XWayland keyboard grab protocol #1093

Merged
merged 1 commit into from
Aug 9, 2023

Conversation

ids1024
Copy link
Member

@ids1024 ids1024 commented Aug 5, 2023

No description provided.

Copy link
Member

@Drakulix Drakulix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

src/wayland/xwayland_keyboard_grab.rs Outdated Show resolved Hide resolved
@ids1024 ids1024 force-pushed the xwayland-keyboard-grab branch 4 times, most recently from aa79729 to c970dbf Compare August 8, 2023 22:51
@ids1024
Copy link
Member Author

ids1024 commented Aug 9, 2023

Would it be better for Smithay to call set_grab here, instead of requiring a grab handler method? That's what is done for input-method. Is there any reason a compositor would want to do something other than just setting the grab like the Anvil implementation here?

Or it could provide a default implementation for the grab method, at least.

@Drakulix
Copy link
Member

Drakulix commented Aug 9, 2023

Would it be better for Smithay to call set_grab here, instead of requiring a grab handler method? That's what is done for input-method. Is there any reason a compositor would want to do something other than just setting the grab like the Anvil implementation here?

Or it could provide a default implementation for the grab method, at least.

Default implementation is fine, but given the protocol explicitly does not guarantee the grab to be set and suggest compositors might even show indicators for keys being captured, I say this should be compositor policy.

This protocol is only exposed to the X server, as required by the
protocol spec.
@codecov-commenter
Copy link

codecov-commenter commented Aug 9, 2023

Codecov Report

Patch coverage: 100.00% and project coverage change: -0.01% ⚠️

Comparison is base (bb25baf) 24.01% compared to head (fe9beab) 24.01%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1093      +/-   ##
==========================================
- Coverage   24.01%   24.01%   -0.01%     
==========================================
  Files         140      140              
  Lines       21589    21591       +2     
==========================================
- Hits         5185     5184       -1     
- Misses      16404    16407       +3     
Flag Coverage Δ
wlcs-buffer 21.03% <100.00%> (+<0.01%) ⬆️
wlcs-core 20.66% <100.00%> (+<0.01%) ⬆️
wlcs-output 8.46% <100.00%> (+<0.01%) ⬆️
wlcs-pointer-input 22.71% <100.00%> (+0.06%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed Coverage Δ
anvil/src/state.rs 38.46% <100.00%> (+0.32%) ⬆️

... and 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@ids1024 ids1024 changed the title WIP XWayland keyboard grab protocol XWayland keyboard grab protocol Aug 9, 2023
@ids1024 ids1024 marked this pull request as ready for review August 9, 2023 20:02
Copy link
Member

@Drakulix Drakulix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Drakulix Drakulix merged commit 02ccc8c into Smithay:master Aug 9, 2023
36 checks passed
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.

3 participants