From 48aeb512e9c9492cb7b5ccf642795af7b4b97cd6 Mon Sep 17 00:00:00 2001 From: Tarandeep Singh Date: Mon, 17 Jul 2017 11:22:52 -0700 Subject: [PATCH] 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 --- services/inputflinger/InputDispatcher.cpp | 5 +---- 1 file changed, 1 insertion(+), 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) { -- 2.11.0