-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Touchscreen does not work on Linux #1763
Comments
I don't have any Linux device with touchscreen support so I can't test it. But it looks like |
If possible, please open a branch and push a change so that Actions can compile a build. I have the device to test it on, if it is the issue it wouldn't be too difficult (?) |
It's not difficult but time consuming as there's a lots of ScrollView also I've to think of ways to detect that display has touch support. Because otherwise in non-touch devices, users will be able to scroll using mouse drag which is not a standard behavior for desktop apps |
Alright, ping me when you are ready. |
Using this on my Linux phone, works absolutely brilliantly, except for scrolling. Maybe look at FluffyChat, they got it working. That one is also a Flutter application. :D |
@rcky844 Can you try out the nightly version now? I forgot to ping u 😅 |
I finally got time to test it, confirmed working 👍 |
Is there an existing issue for this?
Current Behavior
When attempting to scroll in the application with a touchscreen on Linux (Arch Linux in my case), nothing happens, and instead the list entries are selected if I happen to be pressing on it.
Expected Behavior
The pages should scroll as usual, like on mobile variants.
Steps to reproduce
The above description is enough for describing this bug.
Operating System
Arch Linux
Spotube version
3.7.1
Installation source
Arch User Repository (AUR)
Additional information
I am not a Flutter developer, but I found an open issue in one of their repos regarding similar issues:
https://github.com/flutter/flutter/issues/90366
Self grab
The text was updated successfully, but these errors were encountered: