Search Issue Tracker
Won't Fix
Votes
0
Found in
4.3.0f1
Issue ID
572779
Regression
No
One finger WP8 touchscreen taps are consecutively registered on separate touches
1. Create a project which displays info for every touchscreen touch
2. Deploy it to device
3. Start tapping screen with one finger at the same place
4. Notice that, even though there were no simultaneous physical touches on the screen, device registers tap counts on two separate touches.
Why is this not going to be fixed?
There is no way to find out whether subsequent touches came from the same finger or not, as OS gives unique finger ID for each touch event. Unlike on Android, where repeatedly hitting with one finger gives same finger ID every time. Since destruction of touch slot is delayed for 150 milliseconds, hitting twice faster than that will cause second event registered to the second slot.
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
tigerishwillo
Jan 30, 2015 15:10
This bug has caused me issues too, it means that on my endless runner I have to implement platform specific code for Windows devices which is not ideal.