Lines Matching full:link
3 parent.link=index.html
7 previous.link=custom-drawing.html
9 next.link=optimizing-view.html
62 most common input event in the Android system is <em>touch</em>, which triggers {@link
77 provides {@link android.view.GestureDetector}.</p>
79 <p>Construct a {@link android.view.GestureDetector} by passing in an instance of a class that
80 implements {@link
82 can extend {@link
83 android.view.GestureDetector.SimpleOnGestureListener} instead of implementing the {@link
85 interface. For instance, this code creates a class that extends {@link
86 android.view.GestureDetector.SimpleOnGestureListener} and overrides {@link
99 <p>Whether or not you use {@link
101 {@link android.view.GestureDetector.OnGestureListener#onDown onDown()} method that
103 {@link android.view.GestureDetector.OnGestureListener#onDown onDown()} message. If
105 false} from {@link android.view.GestureDetector.OnGestureListener#onDown onDown()}, as
106 {@link android.view.GestureDetector.SimpleOnGestureListener} does, the system assumes that
109 {@link android.view.GestureDetector.OnGestureListener} never get called. The
111 return {@code false} from {@link android.view.GestureDetector.OnGestureListener#onDown onDown()}
114 Once you've implemented {@link android.view.GestureDetector.OnGestureListener}
115 and created an instance of {@link android.view.GestureDetector}, you can use
116 your {@link android.view.GestureDetector} to interpret the touch events you receive in {@link
133 <p>When you pass {@link android.view.GestureDetector#onTouchEvent onTouchEvent()} a touch event that
155 {@link android.widget.Scroller} class is the basis for handling flywheel-style <em>fling</em>
158 <p>To start a fling, call {@link android.widget.Scroller#fling fling()} with the starting velocity
161 you by {@link android.view.GestureDetector}.</p>
172 {@link android.view.GestureDetector} is physically accurate,
178 <p>The call to {@link android.widget.Scroller#fling fling()} sets up the physics model for the fling
180 Afterwards, you need to update the {@link android.widget.Scroller Scroller} by calling {@link
182 intervals. {@link
183 android.widget.Scroller#computeScrollOffset computeScrollOffset()} updates the {@link
187 at that time. Call {@link android.widget.Scroller#getCurrX} and {@link
191 <p>Most views pass the {@link android.widget.Scroller Scroller} object's x and y position directly to
192 {@link
204 <p>The {@link android.widget.Scroller Scroller} class computes scroll positions for you, but it does
211 <li>Call {@link android.view.View#postInvalidate() postInvalidate()} after calling
212 {@link android.widget.Scroller#fling(int, int, int, int, int, int, int, int) fling()},
215 technique requires that you compute scroll offsets in {@link android.view.View#onDraw onDraw()}
216 and call {@link android.view.View#postInvalidate() postInvalidate()} every
219 <li>Set up a {@link android.animation.ValueAnimator} to animate for the duration of the fling,
221 by calling {@link android.animation.ValueAnimator#addUpdateListener addUpdateListener()}.
228 invalidation. The drawback is that {@link android.animation.ValueAnimator}
232 <p class="note"><strong>Note:</strong> {@link android.animation.ValueAnimator} isn't available
266 property directly. Instead, use {@link android.animation.ValueAnimator} to make the change. In
271 in the selected slice. {@link android.animation.ValueAnimator} changes the rotation over a
283 <p>If the value you want to change is one of the base {@link android.view.View} properties, doing
286 because Views have a built-in {@link android.view.ViewPropertyAnimator} that is optimized for
