Lines Matching refs:pointer
54 <li>{@link android.view.MotionEvent#ACTION_DOWN}—For the first pointer that
55 touches the screen. This starts the gesture. The pointer data for this pointer is
58 extra pointers that enter the screen beyond the first. The pointer data for this
59 pointer is at the index returned by {@link android.support.v4.view.MotionEventCompat#getActionIndex…
61 …rt.v4.view.MotionEventCompat#ACTION_POINTER_UP}—Sent when a non-primary pointer goes up.</li>
62 …<li>{@link android.view.MotionEvent#ACTION_UP}—Sent when the last pointer leaves the screen.…
66 android.view.MotionEvent} via each pointer's index and ID:</p>
70 stores information about each pointer in an array. The index of a pointer is its position
73 pointer index as a parameter, not the pointer ID. </li>
76 <li><strong>ID</strong>: Each pointer also has an ID mapping that stays
77 persistent across touch events to allow tracking an individual pointer across
83 undefined. Thus the index of a pointer can change from one event to the
84 next, but the pointer ID of a pointer is guaranteed to remain constant as long
85 as the pointer remains active. Use the {@link
87 pointer's ID to track the pointer across all subsequent motion events in a
90 the pointer index for a given pointer ID in that motion event. For example:</p>
97 // Get the pointer ID
102 // Use the pointer ID to find the index of the active pointer
105 // Get the pointer's current position
119 being performed, without including the pointer index bits. You can then use
121 the pointer associated with the action. This is illustrated in the snippet below.</p>
134 // Get the index of the pointer associated with the action.