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

x11: Use xinput2, and ignore key repetition #1535

Merged
merged 2 commits into from
Sep 18, 2024
Merged

Conversation

ids1024
Copy link
Member

@ids1024 ids1024 commented Sep 16, 2024

The winit backend (and libinput backend) already don't produce key repeat events like this.

@ids1024 ids1024 force-pushed the input branch 2 times, most recently from 05fb5f1 to 313d1ca Compare September 17, 2024 14:56
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.

Needs rebase

If we require dri3 and present, it should be fair to assume xinput2 as
well. This will be needed if we want to add touch and gesture events,
etc.
This backend should avoid producing key press events for key repeat,
the libinput backend.

You can see in `wev` that this prevents repeated key press events on
held keys that don't happen with libinput.
@Drakulix Drakulix merged commit d5693af into Smithay:master Sep 18, 2024
13 checks passed
ids1024 added a commit to pop-os/cosmic-comp that referenced this pull request Sep 18, 2024
Not supressing key repetition in backends seems like it was a bug, and
should be fixed as of Smithay/smithay#1535.

So an argument for this should be unnecessary now.
Drakulix pushed a commit to pop-os/cosmic-comp that referenced this pull request Sep 19, 2024
Not supressing key repetition in backends seems like it was a bug, and
should be fixed as of Smithay/smithay#1535.

So an argument for this should be unnecessary now.
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.

2 participants