Chromium Code Reviews| Index: ui/base/touch/touch_device_android.cc |
| diff --git a/ui/base/touch/touch_device_android.cc b/ui/base/touch/touch_device_android.cc |
| index 39e34c24765363d439e175cad62cdc98ef257ed8..dce717842ee7bbd7a61225e7e20575e3bf3b3daa 100644 |
| --- a/ui/base/touch/touch_device_android.cc |
| +++ b/ui/base/touch/touch_device_android.cc |
| @@ -10,4 +10,21 @@ bool IsTouchDevicePresent() { |
| return true; |
| } |
| +bool CanDetectMaxTouchPoints() { |
| + return false; |
| +} |
| + |
| +// Looks like the best we can do here is detect 1, 2+, or 5+ by |
| +// feature detecting: |
| +// FEATURE_TOUCHSCREEN (1), |
| +// FEATURE_TOUCHSCREEN_MULTITOUCH (2), |
| +// FEATURE_TOUCHSCREEN_MULTITOUCH_DISTINCT (2+), or |
| +// FEATURE_TOUCHSCREEN_MULTITOUCH_JAZZHANDS (5+) |
| +// |
| +// Probably start from the biggest and detect down the list until we |
| +// find one that's supported and return its value. |
|
Rick Byers
2013/10/10 22:42:40
Oh, I'm surprised! That sucks.
Let's leave the d
|
| +int MaxTouchPoints() { |
| + return -1; |
| +} |
| + |
| } // namespace ui |