summaryrefslogtreecommitdiff
path: root/libs/androidfw/ZipFileRO.cpp
diff options
context:
space:
mode:
author Prabir Pradhan <prabirmsp@google.com> 2024-06-06 22:08:05 +0000
committer Prabir Pradhan <prabirmsp@google.com> 2024-06-11 02:42:11 +0000
commit2a51874772630d62b25fd909fb430ad770fa072c (patch)
tree5c88764bc0e520a5908d2e3f7670cb69e334b211 /libs/androidfw/ZipFileRO.cpp
parent4c5d39871b52559b004e40dd5669134ad24187c1 (diff)
MotionEvent: Ensure addBatch works in the current coordinate space
The PointerCoords added via addBatch() are expected to be in the "current" coordinate space of the event. If the event was transformed before the batch was added, it should not affect the coordinate space of the current batch. To ensure coordinate consistency, we need to transfom the newly added PointerCoords by the event's inverse transform so that we get the same values out of the event. Bug: 342349872 Test: atest MotionEventTest Change-Id: I1a25fd6bf0f600b77b3c35cf2ef6d567f996b5dc
Diffstat (limited to 'libs/androidfw/ZipFileRO.cpp')
0 files changed, 0 insertions, 0 deletions