diff options
| author | 2024-08-23 11:11:13 +0000 | |
|---|---|---|
| committer | 2024-08-27 16:23:49 +0000 | |
| commit | 727b15d9cdbbe58f3ccca1f8dbef23e0dd41a5fa (patch) | |
| tree | b58ac1e3f9a3ba0ae86eead07700d637e0312021 /libs/gui/ConsumerBase.cpp | |
| parent | 8b70f29fb22545806461513fdbae3e5aba28fd98 (diff) | |
CapturedTouchpadEventConverter: report relative axes
In the old touchpad stack, when a touchpad was captured we'd report
AXIS_RELATIVE_(X|Y) values for each finger, as offsets from the location
it had in the previous frame. When I implemented captured mode in the
new stack I didn't realize this, so the new stack introduced in Android
U doesn't report them. This causes problems for games that capture the
mouse pointer and use the relative axes for camera movement.
Bug: 330522990
Test: check the axis values using a test app
Test: $ atest inputflinger_tests:CapturedTouchpadEventConverterTest
Flag: com.android.input.flags.include_relative_axis_values_for_captured_touchpads
Change-Id: I8a1caa4c9315dd41bc712fd9467146bb608cf6f3
Diffstat (limited to 'libs/gui/ConsumerBase.cpp')
0 files changed, 0 insertions, 0 deletions