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

The answer gesture is reflected when natural scrolling is on #28414

Closed
alba4k opened this issue Sep 16, 2024 · 5 comments
Closed

The answer gesture is reflected when natural scrolling is on #28414

alba4k opened this issue Sep 16, 2024 · 5 comments

Comments

@alba4k
Copy link

alba4k commented Sep 16, 2024

Steps to reproduce

Simply trying to use the 1:1 gesture to answer to a message will have the direction the message moves in inverted

Expected behaviour

The message should follow the movement of the fingers (just like it works fine in firefox)

Actual behaviour

The direction is opposite

Operating system

Arch Linux, Hyprland

Version of Telegram Desktop

5.5.5

Installation source

Other (unofficial) source

Crash ID

No response

Logs

video_2024-09-16_19-58-58.mp4
@alba4k alba4k added the bug label Sep 16, 2024
@ilya-fedin
Copy link
Contributor

tdesktop does check QWheelEvent::inverted property and reacts accordingly. That's all it can do. If it doesn't work for you, you have a bug somewhere on system level.

@alba4k
Copy link
Author

alba4k commented Sep 21, 2024

@ilya-fedin apparently that spec just doesn't work under wayland? maybe just in kde?

hyprwm/Hyprland#7836 (comment)

why can't this be forced using a toggle?

@ilya-fedin
Copy link
Contributor

apparently that spec just doesn't work under wayland? maybe just in kde?

Maybe? That doesn't mean other compositors can't implement the same.

hyprwm/Hyprland#7836 (comment)

I heard the inverted property is implemented for the Wayland QPA backend. The X11 QPA backend indeed doesn't have support for this. I think hyprland developer can see how to integate with Qt by looking at qtwayland source code.

why can't this be forced using a toggle?

The policy is to have as less settings as possible. That's really something that the system should provide via some API. And that's not a problem for 99% of the users (Linux is only 1% of tdesktop userbase).

@ilya-fedin
Copy link
Contributor

This seem to look like wayland is pretty aware of natural scrolling?
https://gitlab.freedesktop.org/wayland/wayland/-/blob/main/protocol/wayland.xml#L2385

@alba4k
Copy link
Author

alba4k commented Sep 22, 2024

And that's not a problem for 99% of the users (Linux is only 1% of tdesktop userbase).

Such a toggle would also be relevant for just 1% of users, wouldn't have to be visible otherwise

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants