summaryrefslogtreecommitdiff
path: root/core/java/android/view/InputEventConsistencyVerifier.java
Commit message (Collapse)AuthorAgeFilesLines
* Use new UnsupportedAppUsage annotation.Artur Satayev2019-12-181-1/+1
| | | | | | | | Existing annotations in libcore/ and frameworks/ will deleted after the migration. This also means that any java library that compiles @UnsupportedAppUsage requires a direct dependency on "unsupportedappusage" java_library. Bug: 145132366 Test: m && diff unsupportedappusage_index.csv Change-Id: I5be7335b23a92b8ac80d2fd890198273b66ad644
* Add @UnsupportedAppUsage annotationsMathew Inwood2018-08-201-0/+5
| | | | | | | | | | | | | | | | | | | | | | For packages: android.view.textservice android.view.textclassifier.logging android.view.textclassifier android.view.inputmethod android.view.autofill android.view.accessibility android.view This is an automatically generated CL. See go/UnsupportedAppUsage for more details. Exempted-From-Owner-Approval: Mechanical changes to the codebase which have been approved by Android API council and announced on android-eng@ Bug: 110868826 Test: m Change-Id: I4147b038ed7adf0311ee9918b44766f82a057eaf
* Only require that system UIDs tag their sockets.Jeff Sharkey2017-06-271-1/+1
| | | | | | | | | | | | | Apps with a normal UID are typically isolated enough to not require socket tagging; we're mostly interested in tracking down internal UIDs that have lots of code sharing the same UID. Also fix up everyone doing manual string checks of Build.TYPE, since we now have first-class fields for those. Bug: 38126076 Test: builds, boots Change-Id: I3a40348196bd8459289f2b9355d9783a07f1e7dd
* Revert "Revert "Add new MotionEvent actions for button press and release.""Michael Wright2015-05-141-0/+71
| | | | This reverts commit 96238051621ba2dc8a1c20fa48a00ec6ec4735d6.
* Revert "Add new MotionEvent actions for button press and release."Michael Wright2015-05-141-71/+0
| | | | This reverts commit ec0ce51b733f10c620cb9447b074f022d042e31d.
* Add new MotionEvent actions for button press and release.Michael Wright2015-05-141-0/+71
| | | | | | | | | | | | | | Introduce ACTION_BUTTON_PRESS and ACTION_BUTTON_RELEASE as actions to signal a button press or release. If these actions happen simulanteously with a DOWN or UP event then they're explicitly ordered to happen after the DOWN or preceding the UP in order to send them to the most recently targeted view. Also, introduce new stylus button constants that differ from the constants we use for mouse buttons. Bug: 20704355 Change-Id: I5b75e5c5e692171c1c117ee687dd185a0d9dd15c
* Remove reflection from InputEventConsistencyVerifier ctor.Michael Wright2014-05-131-1/+1
| | | | | | | | | InputEventConsistencyVerifier can be instantiated during performTraversals, so we should probably not perform reflection when it isn't necessary. Bug: 14899726 Change-Id: Ia722fdc2de469b1ea6463c6523e18a85ddfbc110
* IME support for trackball and generic motion eventsVictoria Lease2012-09-101-1/+1
| | | | | | | | | | | | | | | Trackball and generic motion events now pass through the IME in case it would like to handle them before passing them on to the view hierarchy. While I was at it, I also... ...fixed the documentation on InputMethodService.onKeyUp() ...added documentation to InputMethodService.onTrackballEvent() ...added trackball and generic motion events to the "input" command ...fixed input consistency verification involving ACTION_OUTSIDE Bug: 7050005 Change-Id: I40ab68df4a9542af6df25de6ec2ec500e4c02902
* Refactor InputQueue as InputEventReceiver.Jeff Brown2011-12-011-5/+6
| | | | | | | | | | | | | This change simplifies the code associated with receiving input events from input channels and makes it more robust. It also does a better job of ensuring that input events are properly recycled (sometimes we dropped them on the floor). This change also adds a sequence number to all events, which is handy for determining whether we are looking at the same event or a new one, particularly when events are recycled. Change-Id: I4ebd88f73b5f77f3e150778cd550e7f91956aac2
* Improve input event consistency invariants.Jeff Brown2011-06-281-14/+13
| | | | | | | | | | | | | Fixed some issues where inconsistent streams of events could be generated by the dispatcher, particularly when switching from hovering with one device to hovering with another. Fixed a bug where the touch pad would fail to generate a new HOVER_MOVE following a tap event. As a result, the hover event stream would not resume until the user touched the touch pad again. Change-Id: I444dce84641fb12e56a0af84c931520771d6c493
* Fix taint and nesting bugs.Jeff Brown2011-06-211-37/+40
| | | | | | | | | | | Tainted events should still be processed, even if we don't bother the developer with the details. The check for nested calls to the event verifier must incorporate the event type because different event types might be overridden in different subclasses so the nesting depths may vary. Change-Id: If2fb213e07db783a0bd1da97bb12aad93126d712
* Touch exploration feature, event bubling, refactorSvetoslav Ganov2011-04-221-2/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | 1. Added an Input Filter that interprets the touch screen motion events to perfrom accessibility exploration. One finger explores. Tapping within a given time and distance slop on the last exlopred location does click and long press, respectively. Two fingers close and in the same diretion drag. Multiple finglers or two fingers in different directions or two fingers too far away are delegated to the view hierarchy. Non moving fingers "accidentally grabbed the device for the scrren" are ignored. 2. Added accessibility events for hover enter, hover exit, touch exoloration gesture start, and end. Accessibility hover events are fired by the hover pipeline. An accessibility event is dispatched up the view tree and the topmost view fires it. Thus predecessors can augment the fired event. An accessibility event has several records and a predecessor can optionally modify, delete, and add such to the event. 3. Added onPopulateAccessibilityEvent and refactored the existing accessibility code to use it. 4. Added API for querying the currently enabled accessibility services by feedback type. Change-Id: Iea2258c07ffae9491071825d966dc453b07e5134
* Revert "Touch exploration feature, event bubling, refactor"Adam Powell2011-04-221-17/+2
| | | | | | | | | This reverts commit ac84d3ba81f08036308b17e1ab919e43987a3df5. There seems to be a problem with this API change. Reverting for now to fix the build. Change-Id: Ifa7426b080651b59afbcec2d3ede09a3ec49644c
* Touch exploration feature, event bubling, refactorSvetoslav Ganov2011-04-211-2/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | 1. Added an Input Filter that interprets the touch screen motion events to perfrom accessibility exploration. One finger explores. Tapping within a given time and distance slop on the last exlopred location does click and long press, respectively. Two fingers close and in the same diretion drag. Multiple finglers or two fingers in different directions or two fingers too far away are delegated to the view hierarchy. Non moving fingers "accidentally grabbed the device for the scrren" are ignored. 2. Added accessibility events for hover enter, hover exit, touch exoloration gesture start, and end. Accessibility hover events are fired by the hover pipeline. An accessibility event is dispatched up the view tree and the topmost view fires it. Thus predecessors can augment the fired event. An accessibility event has several records and a predecessor can optionally modify, delete, and add such to the event. 3. Added onPopulateAccessibilityEvent and refactored the existing accessibility code to use it. 4. Added API for querying the currently enabled accessibility services by feedback type. Change-Id: Iec03c6c3fe298de3f14cb6efdbb9b198cd531a0c
* Track unhandled input events in consistency verifiers.Jeff Brown2011-04-191-6/+83
| | | | | | | | | | This fixes spurious verification errors that would be generated when a view declined an initial event such as ACTION_DOWN. Since the view would not receive the rest of the event stream, it would not see the corresponding ACTION_UP and the next ACTION_DOWN would trigger a spurious verification error. Change-Id: I2386acf378cd1765d5446faed5ad9c6525f8b400
* Add a little input event consistency verifier.Jeff Brown2011-03-311-0/+638
The idea is to assist with debugging by identifying cases in which the input event stream is corrupted. Change-Id: I0a00e52bbe2716be1b3dfc7c02a754492d8e7f1f
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-12 14:29:49 +0000