Home
last modified time | relevance | path

Searched refs:gestures (Results 1 – 25 of 52) sorted by relevance

123

/frameworks/base/core/java/android/gesture/
DGestureStore.java152 ArrayList<Gesture> gestures = mNamedGestures.get(entryName); in addGesture() local
153 if (gestures == null) { in addGesture()
154 gestures = new ArrayList<Gesture>(); in addGesture()
155 mNamedGestures.put(entryName, gestures); in addGesture()
157 gestures.add(gesture); in addGesture()
171 ArrayList<Gesture> gestures = mNamedGestures.get(entryName); in removeGesture() local
172 if (gestures == null) { in removeGesture()
176 gestures.remove(gesture); in removeGesture()
179 if (gestures.isEmpty()) { in removeGesture()
206 ArrayList<Gesture> gestures = mNamedGestures.get(entryName); in getGestures() local
[all …]
/frameworks/base/docs/html/training/gestures/
Dindex.jd24 <li>Design Guide for <a href="{@docRoot}design/patterns/gestures.html">Gestures</a></li>
40 app via touch gestures. Android provides a variety of APIs to
41 help you create and detect gestures.</p>
43 <p>Although your app should not depend on touch gestures for basic behaviors (since the gestures
49 the accepted Android conventions for touch gestures. The <a
50 href="http://developer.android.com/design/patterns/gestures.html">Gestures
52 shows you how to use common gestures in Android apps. Also see the Design Guide
63 … Learn how to detect basic touch gestures such as scrolling, flinging, and double-tapping, using
86 Learn how to detect multi-pointer (finger) gestures.
Ddetector.jd29 <li>Design Guide for <a href="{@docRoot}design/patterns/gestures.html">Gestures</a></li>
53 gestures your app supports. </li>
130 common gestures such as double tap, long press, fling, and so on, you can
134 gestures without processing the individual touch events yourself. This is
167 common gestures. Some of the gestures it supports include {@link
283 <p>If you only want to process a few gestures, you can extend {@link
300 method that returns {@code true}. This is because all gestures begin with an
Dmovement.jd28 <li>Design Guide for <a href="{@docRoot}design/patterns/gestures.html">Gestures</a></li>
55 To help apps distinguish between movement-based gestures (such as a swipe) and
56 non-movement gestures (such as a single tap), Android includes the notion of
97 is useful for gestures in which velocity is part of the criteria for the
Dscale.jd30 <li>Design Guide for <a href="{@docRoot}design/patterns/gestures.html">Gestures</a></li>
45 <p>This lesson describes how to use touch gestures to drag and scale on-screen
188 built-in support for common gestures. It overrides
267 {@link android.view.GestureDetector} helps you detect common gestures used by
271 be used together when you want a view to recognize additional gestures.</p>
351 * The scale listener, used for handling multi-finger scale gestures.
Dmulti.jd29 <li>Design Guide for <a href="{@docRoot}design/patterns/gestures.html">Gestures</a></li>
45 at the same time. This lesson describes how to detect gestures that involve
Dscroll.jd29 <li>Design Guide for <a href="{@docRoot}design/patterns/gestures.html">Gestures</a></li>
50 a scrolling effect in response to touch gestures using <em>scrollers</em>.
149 // user manipulates via touch gestures.
/frameworks/base/docs/html/tools/testing/
Dtesting_accessibility.jd18 <li><a href="#test-gestures">Testing gesture navigation</a></li>
77 than accessibility gestures. While gestures allow users to focus on nearly any on-screen
91 <li><strong>Gestures work with TalkBack enabled:</strong> Verify that app-specific gestures,
93 continue to work when <a href="#testing-talkback">TalkBack is enabled</a>. If these gestures do
229 <h3 id="test-gestures">Testing gesture navigation</h3>
233 <a href="https://support.google.com/accessibility/android/answer/6006598">gestures</a>. This
236 <p class="note"><strong>Note:</strong> Accessibility gestures provide a different navigation path
237 than keyboards and D-pads. While gestures allow users to focus on nearly any on-screen
244 features are enabled, accessibility gestures are automatically enabled.</li>
246 Settings &gt; Manage shortcut gestures</strong>.
[all …]
/frameworks/base/docs/html/training/
Dbest-user-input.jd9 touch screen gestures and text input through on-screen input methods and hardware keyboards.</p>
Dtraining_toc.cs1413 <a href="<?cs var:toroot ?>training/gestures/index.html"
1415 … "How to write apps that allow users to interact with the touch screen via touch gestures."
1419 <li><a href="<?cs var:toroot ?>training/gestures/detector.html">
1423 <li><a href="<?cs var:toroot ?>training/gestures/movement.html">
1427 <li><a href="<?cs var:toroot ?>training/gestures/scroll.html">
1431 <li><a href="<?cs var:toroot ?>training/gestures/multi.html">
1435 <li><a href="<?cs var:toroot ?>training/gestures/scale.html">
1439 <li><a href="<?cs var:toroot ?>training/gestures/viewgroup.html">
/frameworks/base/docs/html/design/style/
Dtouch-feedback.jd9 of gestures, and indicate what actions are enabled and disabled.</p>
53 <p>When your objects react to more complex gestures, help users
/frameworks/base/docs/html/training/custom-views/
Dmaking-interactive.jd74 terms of gestures
76 gestures, Android
81 android.view.GestureDetector.OnGestureListener}. If you only want to process a few gestures, you
102 returns {@code true}. This step is necessary because all gestures begin with an
156 gestures.</p>
Dindex.jd58 <dd>Users expect a view to react smoothly and naturally to input gestures.
Doptimizing-view.jd37 <p>Now that you have a well-designed view that responds to gestures and transitions between states,
/frameworks/base/docs/html/guide/topics/ui/accessibility/
Dservices.jd22 <li><a href="#detect-gestures">Listening for gestures</a></li>
328 <a href="{@docRoot}tools/testing/testing_accessibility.html#test-gestures">gesture navigation</a>,
332 <h3 id="detect-gestures">Listening for gestures</h3>
334 <p>Accessibility services can listen for specific gestures and respond by taking action on behalf
356 receives notification of accessibility gestures through your service's
423 testing accessibility gestures. For more information about testing this feature, see
424 <a href="{@docRoot}tools/testing/testing_accessibility.html#test-gestures">Testing gesture
/frameworks/base/docs/html/about/versions/
Dandroid-1.6-highlights.jd167 <p>A new gestures framework provides application developers with a framework for creating, storing,
168 loading, and recognizing gestures and associating them with specific actions.</p>
171 of gestures to include with their application.</p>
/frameworks/base/docs/html/guide/topics/location/
Dindex.jd75 map display, and touch gestures on the map. You can also use API calls to add markers,
85 keypresses and touch gestures to pan and zoom the map automatically, including
/frameworks/base/docs/html/design/building-blocks/
Dtabs.jd17 <p>For details on using gestures to move between tabs, see the <a href="{@docRoot}design/patterns/s…
/frameworks/base/docs/html/design/patterns/
Dnew.jd98 The updated <a href="{@docRoot}design/patterns/gestures.html">Gestures</a>
99 page covers new and updated gestures introduced in Android KitKat:
101 gestures are used for changing the viewing size of content.
Dbuttons.jd87 This rule also applies to any app-specific gestures you might have for hiding
135 touches or gestures anywhere outside the system bars.
Dfullscreen.jd87 This rule also applies to any app-specific gestures you might have for hiding
135 touches or gestures anywhere outside the system bars.
Dwidgets.jd63 <p>The only gestures available for widgets are:</p>
71 …ion limitations, some of the UI building blocks that rely on restricted gestures are not available…
/frameworks/base/docs/html/design/wear/
Dprinciples.jd34 <h2 id="BigGestures">Design for big gestures</h2>
42 …ng or stop the conversation to be precise, you should consider how your gestures could be bigger.<…
/frameworks/base/docs/html/guide/topics/manifest/
Duses-feature-element.jd796 with a fake touch interface will not support all two-finger gestures, because the input is
797 being transformed to cursor movement on the screen. That is, single finger gestures on such a device
799 gestures will result in the corresponding two-finger touch event. An example device that supports
813 with a fake touch interface will not support all five-finger gestures, because the input is being
814 transformed to cursor movement on the screen. That is, single finger gestures on such a device move
815 a cursor; multi-finger gestures will result in single-finger touch events; other multi-finger
816 gestures will result in the corresponding multi-finger touch event. An example device that supports
823 <td>The application uses touchscreen capabilities for gestures that are more interactive
833 gestures such as a fling), then you don't need to do anything, because this is required by default.
836 <p>If you require more complex touch interaction, such as multi-finger gestures, you
[all …]
/frameworks/base/docs/html/training/material/
Dget-started.jd115 gestures</a>.</p>

123