-
Notifications
You must be signed in to change notification settings - Fork 41
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
Touchpad Scroll on Wayland not working #2236
Comments
Is this KWin-specific or do you see the same on Mutter? |
I'm also on KWin and can reproduce there. |
But is it related to KWin or does Gnome give the same? |
FWIW, I can't reproduce this on FreeBSD running sway |
Works like a charm when using the |
Scrolling events come in two modes, pixel-based and angle-based. On we get deltas of the form
Events on Wayland have --> How are we supposed to use the pixel deltas in the first place? They don't feel like pixel differences at all. |
Qt itself uses |
Using pixelDelta() resulted in seemingly meaningless values on KWin/Wayland. Qt code uses angleDelta() exclusively, so I see no reason not to do the same. Closes longturn#2236.
Using pixelDelta() resulted in seemingly meaningless values on KWin/Wayland. Qt code uses angleDelta() exclusively, so I see no reason not to do the same. Closes longturn#2236.
Using pixelDelta() resulted in seemingly meaningless values on KWin/Wayland. Qt code uses angleDelta() exclusively, so I see no reason not to do the same. Closes #2236.
Using pixelDelta() resulted in seemingly meaningless values on KWin/Wayland. Qt code uses angleDelta() exclusively, so I see no reason not to do the same. Closes #2236.
Describe the bug
The touchpad scroll only works left/right, up/down and not diagonally on Wayland. Is also laggy/slow. Works fine on X11
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Mouse events work same on Wayland as on X11
Screenshots
N/A
Platform and version (please complete the following information):
Additional context
https://discord.com/channels/378908274113904641/1109113177779732550/1215113440033636464
The text was updated successfully, but these errors were encountered: