Resolve associated display and pointer display in CursorInputMapper
An InputDevice can be associated with a display, in which case it should only generate events for that display. A mouse generally generates events for whichever display is currently showing the mouse cursor. In the case where a mouse InputDevice is associated with a display, we need to make sure that it only generates events when the mouse cursor is on the associated display. Additionally, any display-dependent configuration, such as orientation, should depend on whichever display the device is configured for. Bug: 236075874 Test: atest inputflinger_tests Change-Id: I1021c121c1eae768585124d312f5187be90da666 Merged-In: I1021c121c1eae768585124d312f5187be90da666 (cherry picked from commit c13ff081)
Showing
- include/input/PrintTools.h 10 additions, 0 deletionsinclude/input/PrintTools.h
- services/inputflinger/reader/mapper/CursorInputMapper.cpp 35 additions, 25 deletionsservices/inputflinger/reader/mapper/CursorInputMapper.cpp
- services/inputflinger/reader/mapper/CursorInputMapper.h 4 additions, 0 deletionsservices/inputflinger/reader/mapper/CursorInputMapper.h
- services/inputflinger/tests/InputReader_test.cpp 93 additions, 22 deletionsservices/inputflinger/tests/InputReader_test.cpp
Loading
Please register or sign in to comment