core: treat touch as click #788
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
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.
This treats touch input events as (left) clicks.
Currently the onClick implementation does not care which (mouse) button is used to click on an element. So it might be acceptable to remove the include and use a fixed value (0 or 272). However, this might lead to problems if onClick ever learns to distinguish between different clicks.
This only works for "real" finger touch inputs, (tablet) pen touches are translated to pointer move events, but the tab event does not seem to reach hyprlock.
Tested on a surface go 1 and a thinkpad x1 yoga gen1 with arch.