-
-
Notifications
You must be signed in to change notification settings - Fork 173
Multitouch results into first finger not being released. #61
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
Comments
Okay, it's on my to-do list. |
Great, if theres anything i can help you with, just let me know. I had a look on the code, but just didn't even know where to start looking. |
@dbeulen |
Can we have a option to disable multitouch until you fixed the bug to prevent unwanted inputs? |
I just now uploaded the |
We didnt do a very clean job of removing multitouch, but it works for now.... |
So in first place, thanks both for your work! @ardera I tried to compile the
I never had such problems with the master branch but I am running on the lite version so maybe that's just me missing some packages. |
Exactly, you need to have the following additional packages installed: The The dependency on |
I tried this but haven't put "-dev" behind the requested package name. Just because I'm interested - when does a library get this "-dev" sign? But with these packages building worked fine until I wanted to start my app. The main project I'm working on just crashed right after starting it:
Output of the default Flutter app was this:
So this has probably something to do with orientation which you said is not implemented yet. |
I'm using flutter pi on a raspberry pi official touchscreen. However, when you touch the screen whenever a different finger is pressing a widget, the widget will never be released any more. This is tested on a slider and a card, but on both widgets the issue exists.
Flutter version 1.17.3
Flutter-pi version: latest commit on master 94f38d3
Flutter-pi engine: latest on engine binaries branch dcf0d22
To reproduce:
With a Card this issue is a bigger problem, because i cannot recognise a new touch after the problem arises.
The text was updated successfully, but these errors were encountered: