eb8b9d8a22
The touch screen sometimes reports more than 10 pointers even though that's all we asked for. When this happens, we start dropping events with more than 10 pointers. This confuses applications and causes them to crash. Raised the limit to 16 pointers. Bug: 3331247 The default behavior was to identify all touch devices as touch screens. External devices that are plugged in are more likely to be touch pads not attached to a screen. Changed the default to be a touch pad and renamed some internal constants to avoid confusion. A certain mouse happens to also behave like a touch pad. That caused problems because we would see multiple concurrent traces of motion events coming from the same input device so we would batch them up. Added code to ensure that we don't batch events unless they come from the same *source* in addition to coming from the same *device*. Due to batching or misbehaving drivers, it's possible for the set of pointer ids to be different from what we expect when it comes time to split motion events across windows. As a result, we can generate motion events with 0 pointers. When we try to deliver those events, we cause an error in the InputTransport so we tear down the InputChannel and kill the application. Added code to check out assumption about pointer ids and drop the event gracefully instead. Patched up the tests to take into account the change in default behavior for identifying touch screens and touch pads. Change-Id: Ic364bd4cb4cc6335d4a1213a26d6bdadc7e33505 |
||
|---|---|---|
| .. | ||
| egl | ||
| android_native_buffer.h | ||
| DisplayInfo.h | ||
| EGLNativeSurface.h | ||
| EGLUtils.h | ||
| FramebufferNativeWindow.h | ||
| GraphicBuffer.h | ||
| GraphicBufferAllocator.h | ||
| GraphicBufferMapper.h | ||
| GraphicLog.h | ||
| Input.h | ||
| InputTransport.h | ||
| Keyboard.h | ||
| KeyCharacterMap.h | ||
| KeycodeLabels.h | ||
| KeyLayoutMap.h | ||
| PixelFormat.h | ||
| Point.h | ||
| PowerManager.h | ||
| Rect.h | ||
| Region.h | ||
| VirtualKeyMap.h | ||