-
Notifications
You must be signed in to change notification settings - Fork 48
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
Touchend is unreliable in multitouch #37
Comments
feiss
changed the title
Touchend faulty in multitouch
Touchend is unreliable in multitouch
Feb 15, 2015
@feiss - I've fixed it and put your test case online: http://canvasquery.com/toucherror Could you confirm it's gone? |
fixed in iOS! 💃 👍 👍 in Android touchend is not called (no red circles) ps: do you have a life? :P |
Will investigate android as soon as I find my nexus. ps: Since I am crunching Jameson for PAX the answer is close to |
Stop worrying about opened issues then! go go go! 📢 📢 (thanks anyway :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Trying mobile multitouch support, I've notice this unpredictable behaviour. Sometimes touchend is called, sometimes is not, and sometimes is called in a wrong x,y. Test code below and try it on mobile.
The code in the docs (handling multitouch in render()) runs perfectly, but there's no easy way to know if a touch starts or ends.
Tested on iPad mini (ios 7.1.2) and Nexus7 (android 5.0.2). On the nexus, where the frame rate is lower, the effect is worse.
The text was updated successfully, but these errors were encountered: