You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Multitouch.maxTouchPoints return incorrect value with Android devices which support more than 2 touch points simultaneously. Multitouch.maxTouchPoints return 2 in such cases instead of 5.
So using AIR you cannot detect capabilities of touch screen.
Tested with different AIR 50.2 versions (even with latest AIR 50.2.3.3) with multiple different Android devices with different OS versions, different AIR applications and architectures.
Same problem in all cases.
Many years ago in ~AIR 19 all works fine.
Steps to Reproduce
Launch application with code below with any Android device which support more than 2 touch points.
Application example with sources attached. android_maxtouchpoints_bug.zip
trace(Multitouch.maxTouchPoints);
Actual Result: Multitouch.maxTouchPoints return 2.
Problem Description
Multitouch.maxTouchPoints
return incorrect value with Android devices which support more than 2 touch points simultaneously.Multitouch.maxTouchPoints
return2
in such cases instead of5
.So using AIR you cannot detect capabilities of touch screen.
Tested with different AIR 50.2 versions (even with latest AIR 50.2.3.3) with multiple different Android devices with different OS versions, different AIR applications and architectures.
Same problem in all cases.
Many years ago in ~AIR 19 all works fine.
Steps to Reproduce
Launch application with code below with any Android device which support more than 2 touch points.
Application example with sources attached.
android_maxtouchpoints_bug.zip
Actual Result:
Multitouch.maxTouchPoints
return2
.Expected Result:
Multitouch.maxTouchPoints
return5
(in terms of https://developer.android.com/reference/android/content/pm/PackageManager#FEATURE_TOUCHSCREEN_MULTITOUCH_JAZZHAND).Known Workarounds
none
Write native extension for that.
The text was updated successfully, but these errors were encountered: