Commit 48aeb512 authored Jul 17, 2017 by Tarandeep Singh

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

parent 8e0c3f5f

services/inputflinger/InputDispatcher.cpp

+1 −4

Original line number	Diff line number	Diff line
		@@ -869,10 +869,7 @@ bool InputDispatcher::dispatchMotionLocked(
		return true;
		}

		// TODO: support sending secondary display events to input monitors
		if (isMainDisplay(entry->displayId)) {
		addMonitoringTargetsLocked(inputTargets);
		}

		// Dispatch the motion.
		if (conflictingPointerActions) {