| commit | cce7e112242e0400b38c23031056fc278f3f6326 | [log] [tgz] |
|---|---|---|
| author | Siarhei Vishniakou <svv@google.com> | Tue Oct 25 13:31:17 2022 -0700 |
| committer | Siarhei Vishniakou <svv@google.com> | Thu Oct 27 00:57:47 2022 +0000 |
| tree | fea71212e12945e806fd0ac6c2ab1efeed610a60 | |
| parent | 34014048584e8720e2bf26903c20430eb5fb0c02 [diff] |
Separate logic for publishing motion events Before a motion event is published, there's some more processing happening, such as determining which coords should be used. Let's move that into a separate function to make it more tractable. Bug: 211379801 Test: atest inputflinger_tests Change-Id: If373305b546c461e22e4b496d66418f771e9e741