91fa08ff1bd85ae41d71e1ed5ee72357c975ee3b - platform/frameworks/base

commit	91fa08ff1bd85ae41d71e1ed5ee72357c975ee3b	[log] [tgz]
author	Siarhei Vishniakou <svv@google.com>	Fri Jun 08 22:49:30 2018 +0100
committer	Siarhei Vishniakou <svv@google.com>	Thu Jul 05 16:29:51 2018 +0100
tree	78a1d48c0aac3feeeb6212d1af5ac57a4986221f
parent	beac1471aab97797a66542e9fd22e5cfc5447c02 [diff]

Move displayId into InputEvent

Now both KeyEvent and MotionEvent will contain displayId. This will help
with dispatching input events to specific displays. There are use cases
where a particular input device is used for a specific display only, and
it sends key events to the system. This will help with those usages.

Test: atest view.MotionEventTest view.KeyEventTest
Bug: 64258305
Change-Id: I75891037617ed60820d60736216a0d615ab5e3b0

core/java/android/view/InputEvent.java[diff]
core/java/android/view/KeyEvent.java[diff]
core/java/android/view/MotionEvent.java[diff]
core/jni/android_view_InputEventSender.cpp[diff]
core/jni/android_view_KeyEvent.cpp[diff]
core/tests/coretests/src/android/view/KeyEventTest.java[diff]
services/core/java/com/android/server/input/InputForwarder.java[diff]
services/core/jni/Android.bp[diff]

8 files changed

tree: 78a1d48c0aac3feeeb6212d1af5ac57a4986221f