drgreen/android_frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

am 41aabeb5: am 1e6a3a53: Merge "Added more robust tracking and cancelation of events." into gingerbread

Browse Source 
Merge commit '41aabeb51305d19747687f246080f44fc2a74435'

* commit '41aabeb51305d19747687f246080f44fc2a74435':
  Added more robust tracking and cancelation of events.
This commit is contained in:
Jeff Brown
2010-10-11 17:42:30 -07:00
committed by Android Git Automerger
parent 5d3f6073bf 41aabeb513
commit dd8b0c9040
10 changed files with 519 additions and 427 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
core/java/android/view/KeyEvent.java
View File

@ -46,10 +46,12 @@ import android.view.KeyCharacterMap.KeyData;
* with the special action {@link #ACTION_MULTIPLE} that either specifies
* that single repeated key code or a sequence of characters to insert.
* </p><p>
* In general, the framework makes no guarantees that the key events delivered
* to a view constitute a complete key press. In particular, there is no
* guarantee that a view will always receive a key event with {@link #ACTION_UP}
* for each {@link #ACTION_DOWN} that was delivered.
* In general, the framework cannot guarantee that the key events it delivers
* to a view always constitute complete key sequences since some events may be dropped
* or modified by containing views before they are delivered. The view implementation
* should be prepared to handle {@link #FLAG_CANCELED} and should tolerate anomalous
* situations such as receiving a new {@link #ACTION_DOWN} without first having
* received an {@link #ACTION_UP} for the prior key press.
* </p><p>
* Refer to {@link InputDevice} for more information about how different kinds of
* input devices and sources represent keys and buttons.

10
core/java/android/view/MotionEvent.java
View File

@ -82,10 +82,12 @@ import android.os.SystemClock;
* }
* }
* </code></pre></p><p>
* In general, the framework makes no guarantees that the motion events delivered
* to a view constitute a complete gesture. In particular, there is no
* guarantee that a view will always receive a motion event with {@link #ACTION_UP}
* for each {@link #ACTION_DOWN} that was delivered.
* In general, the framework cannot guarantee that the motion events it delivers
* to a view always constitute a complete motion sequences since some events may be dropped
* or modified by containing views before they are delivered. The view implementation
* should be prepared to handle {@link #ACTION_CANCEL} and should tolerate anomalous
* situations such as receiving a new {@link #ACTION_DOWN} without first having
* received an {@link #ACTION_UP} for the prior gesture.
* </p><p>
* Refer to {@link InputDevice} for more information about how different kinds of
* input devices and sources represent pointer coordinates.

2
core/java/android/view/WindowManagerPolicy.java
View File

@ -65,6 +65,7 @@ import android.view.animation.Animation;
* @hide
*/
public interface WindowManagerPolicy {
// Policy flags. These flags are also defined in frameworks/base/include/ui/Input.h.
public final static int FLAG_WAKE = 0x00000001;
public final static int FLAG_WAKE_DROPPED = 0x00000002;
public final static int FLAG_SHIFT = 0x00000004;
@ -79,6 +80,7 @@ public interface WindowManagerPolicy {
public final static int FLAG_WOKE_HERE = 0x10000000;
public final static int FLAG_BRIGHT_HERE = 0x20000000;
public final static int FLAG_PASS_TO_USER = 0x40000000;
public final static boolean WATCH_POINTER = false;