diff options
| author | Tarandeep Singh <tarandeep@google.com> | 2017-07-17 11:22:52 -0700 |
|---|---|---|
| committer | Tarandeep Singh <tarandeep@google.com> | 2017-07-31 15:38:24 -0700 |
| commit | 48aeb512e9c9492cb7b5ccf642795af7b4b97cd6 (patch) | |
| tree | 7e40470362c3e88ae8aa14c63a1dd81088d104f2 | |
| parent | 8e0c3f5f1c4ffc3a055fe016406bd6a549ebdd00 (diff) | |
| download | native-48aeb512e9c9492cb7b5ccf642795af7b4b97cd6.tar.gz | |
Enable InputMonitors for non-default display.
InputFlinger today doesn't deliver InputMonitors for non-deafult
display. In order to support focussing windows on virtual-displays
(like the Vr2dDisplay), we need to be able to send motion events
to them for keyboard to gain focus.
Bug: 62033391
Test: Manual by launching
com.google.vr.vrcore/.daydream.MetaworldActivity & then
com.google.android.apps.nexuslauncher/.NexusLauncherActivity.
Exact steps are mentioned in the bug.
Change-Id: I5954e54cef8c0a29f05bc964debc95ea81f16758
| -rw-r--r-- | services/inputflinger/InputDispatcher.cpp | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/services/inputflinger/InputDispatcher.cpp b/services/inputflinger/InputDispatcher.cpp index 2efb340eba..7bc702d00f 100644 --- a/services/inputflinger/InputDispatcher.cpp +++ b/services/inputflinger/InputDispatcher.cpp @@ -869,10 +869,7 @@ bool InputDispatcher::dispatchMotionLocked( return true; } - // TODO: support sending secondary display events to input monitors - if (isMainDisplay(entry->displayId)) { - addMonitoringTargetsLocked(inputTargets); - } + addMonitoringTargetsLocked(inputTargets); // Dispatch the motion. if (conflictingPointerActions) { |