tree 67cf3ff4e962b5e6816a7f011bc9c7c64ebc8f1e
parent ae0b8d1d9bbada6795d81ab20f7470cb4f3cdc60
author Siarhei Vishniakou <svv@google.com> 1670444586 +0000
committer Siarhei Vishniakou <svv@google.com> 1674143053 -0800

Track hovering pointers explicitly -- try 2

Update:
Compared to the first version of this CL that got reverted, this version
also adds Flags::FOREGROUND to the windows whenever appropriate.

Before this CL, hovering window was tracked separately inside
InputDispatcher. This window was getting updated in various places.
Inconsistent motion streams, like HOVER_ENTER->DOWN->UP->HOVER_EXIT were
possible.

In this CL, we track hovering pointers inside TouchedWindow. At all
times, the currently tracked pointer must always be in the touch state.
The hovering pointer is removed when HOVER_EXIT is received.

This CL also establishes the foundation for multi-device, multi-pointer
streams, by storing hovering pointers inside TouchedWindow per-device.

Eventually, we can look into separately creating touched targets from
updating the touch state. This approach is partially used in this CL.

TouchState is used to keep track of where the hovering pointer is
currently. The 'addHoveringWindowsLocked' function returns the
equivalent of InputTargets. Eventually, we can change this to return
InputTargets.

39d37cfb471c69f924e90f8e35afcff4ad4e6042

Bug: 211379801
Test: atest android.accessibilityservice.cts.AccessibilityEndToEndTest
Test: atest VirtualMouseTest
Test: m inputflinger_tests && adb sync data && adb shell -t /data/nativetest64/inputflinger_tests/inputflinger_tests

Change-Id: I0aa77bc9f680786b154312c4c936da2cf6efffa1