Lines Matching refs:touch

6 analyze touch events on the screen for intentional vs accidental behavior. With analysis, 
12 The `FalsingManager` tracks all touch interactions happening on a phone's lock screen.
14 If you support any sort of touch gestures on the lock screen, you **must**, at a
15 minimum, inform the `FalsingManager` of what touches are on touch targets vs not (things that may be
19 Individual touch targets do not _have_ to be separated out; it's acceptable to
25 the `FalsingManager` that touch events were on touch targets, you can further use the
26 returned results to decide if you want to respond to an owner's touch, if you
28 touch.
34     * If no feature/touch target receives the `MotionEvents`, skip to 4. 
35 3. Your touch target receives the `MotionEvents`.
38       - Dragging animations, touch ripples, and other purely visual effects should not query.
43     * If the `FalsingManager` says it looks good, respond to the touch.
68 The methods below inform the `FalsingManager` that a tap is occurring within an expected touch 
75 all within some small x & y region ("touch slop"). Useful for only the most simple of scenarios,