diff options
author | Jeff Brown <jeffbrown@google.com> | 2010-04-22 18:58:52 -0700 |
---|---|---|
committer | Jeff Brown <jeffbrown@google.com> | 2010-06-13 17:42:16 -0700 |
commit | 46b9ac0ae2162309774a7478cd9d4e578747bfc2 (patch) | |
tree | 46ad021a41e25ca9f1250b709a29b724dc6b504d /core/java/android/view/WindowManagerPolicy.java | |
parent | f62c57d684b83df7d2817db976c0afdb500ae92a (diff) | |
download | frameworks_base-46b9ac0ae2162309774a7478cd9d4e578747bfc2.zip frameworks_base-46b9ac0ae2162309774a7478cd9d4e578747bfc2.tar.gz frameworks_base-46b9ac0ae2162309774a7478cd9d4e578747bfc2.tar.bz2 |
Native input dispatch rewrite work in progress.
The old dispatch mechanism has been left in place and continues to
be used by default for now. To enable native input dispatch,
edit the ENABLE_NATIVE_DISPATCH constant in WindowManagerPolicy.
Includes part of the new input event NDK API. Some details TBD.
To wire up input dispatch, as the ViewRoot adds a window to the
window session it receives an InputChannel object as an output
argument. The InputChannel encapsulates the file descriptors for a
shared memory region and two pipe end-points. The ViewRoot then
provides the InputChannel to the InputQueue. Behind the
scenes, InputQueue simply attaches handlers to the native PollLoop object
that underlies the MessageQueue. This way MessageQueue doesn't need
to know anything about input dispatch per-se, it just exposes (in native
code) a PollLoop that other components can use to monitor file descriptor
state changes.
There can be zero or more targets for any given input event. Each
input target is specified by its input channel and some parameters
including flags, an X/Y coordinate offset, and the dispatch timeout.
An input target can request either synchronous dispatch (for foreground apps)
or asynchronous dispatch (fire-and-forget for wallpapers and "outside"
targets). Currently, finding the appropriate input targets for an event
requires a call back into the WindowManagerServer from native code.
In the future this will be refactored to avoid most of these callbacks
except as required to handle pending focus transitions.
End-to-end event dispatch mostly works!
To do: event injection, rate limiting, ANRs, testing, optimization, etc.
Change-Id: I8c36b2b9e0a2d27392040ecda0f51b636456de25
Diffstat (limited to 'core/java/android/view/WindowManagerPolicy.java')
-rw-r--r-- | core/java/android/view/WindowManagerPolicy.java | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/core/java/android/view/WindowManagerPolicy.java b/core/java/android/view/WindowManagerPolicy.java index b39cb9d..431b786 100644 --- a/core/java/android/view/WindowManagerPolicy.java +++ b/core/java/android/view/WindowManagerPolicy.java @@ -78,6 +78,12 @@ public interface WindowManagerPolicy { public final static int FLAG_BRIGHT_HERE = 0x20000000; public final static boolean WATCH_POINTER = false; + + /** + * Temporary flag added during the transition to the new native input dispatcher. + * This will be removed when the old input dispatch code is deleted. + */ + public final static boolean ENABLE_NATIVE_INPUT_DISPATCH = false; // flags for interceptKeyTq /** @@ -708,6 +714,8 @@ public interface WindowManagerPolicy { */ public boolean preprocessInputEventTq(RawInputEvent event); + public void notifyLidSwitchChanged(long whenNanos, boolean lidOpen); + /** * Determine whether a given key code is used to cause an app switch * to occur (most often the HOME key, also often ENDCALL). If you return |