| /frameworks/base/core/tests/coretests/src/android/widget/ |
| TextViewActivityMouseTest.java | 53 * Tests mouse interaction of the TextView widget from an Activity
|
| /frameworks/base/docs/html/about/versions/ |
| android-1.5.jd | 190 <li>Framework for easier background/UI thread interaction</li>
|
| android-2.2.jd | 153 <li>The platform provides new speech-recognition APIs that allow applications to have a richer interaction with the available voice recognizer. For example, the APIs are sufficient to integrate voice recognition deeply into an IME.</li>
|
| /frameworks/base/docs/html/design/patterns/ |
| widgets.jd | 71 <p>Given the above interaction limitations, some of the UI building blocks that rely on restricted gestures are not available for widgets. For a complete list of supported building blocks and more information on layout restrictions, please refer to the "Creating App Widget Layouts" section in the <a href="{@docRoot}guide/topics/appwidgets/index.html">App Widgets</a> API Guide.</p>
|
| /frameworks/base/docs/html/design/wear/ |
| patterns.jd | 165 <p>Choosing an item from a list is a common interaction. The Selection List pattern (available as the <a
|
| /frameworks/base/docs/html/distribute/googleplay/ |
| wear.jd | 88 require zero or low user interaction. Although all apps can send basic notifications to Wear
|
| /frameworks/base/docs/html/google/play/licensing/ |
| overview.jd | 175 should manage response data, UI interaction, and error conditions. </p>
|
| /frameworks/base/docs/html/guide/practices/ui_guidelines/ |
| icon_design.jd | 100 interaction.</dd>
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| uses-feature-element.jd | [all...] |
| /frameworks/base/docs/html/preview/features/ |
| notification-updates.jd | 185 // handled their interaction with the previous notification.
|
| /frameworks/base/docs/html/training/accessibility/ |
| testing.jd | 47 problems with user interaction that are not obvious during design and development.</p>
|
| /frameworks/base/docs/html/training/articles/ |
| assistant.jd | 65 Figure 1. Assistant interaction example with the Now on Tap feature of
|
| /frameworks/base/docs/html/training/permissions/ |
| requesting.jd | 359 requestPermissions()}, you cannot assume that any direct interaction with the
|
| /frameworks/base/docs/html/training/system-ui/ |
| immersive.jd | 154 interaction, you can probably get by with the <a href="{@docRoot}design/patterns/fullscreen.html">
|
| /frameworks/base/docs/html/training/testing/start/ |
| index.jd | 82 app, and automate user interaction with your app.</p>
|
| /frameworks/base/docs/html/training/transitions/ |
| transitions.jd | 210 example, you can implement a search interaction with just a single layout. Start with the
|
| /frameworks/base/docs/html/training/tv/discovery/ |
| recommendations.jd | 33 The Android framework assists with minimum-input interaction by providing a recommendations row
|
| /frameworks/base/docs/html/training/tv/games/ |
| index.jd | 91 How you shape the player's interaction with the controller can be key to achieving a great user
|
| /frameworks/base/docs/html/training/tv/tif/ |
| ui.jd | 1 page.title=Managing User Interaction
|
| /frameworks/base/docs/html/training/wearables/apps/ |
| creating.jd | 163 long amounts of user interaction. When the app completes these operations, your app should
|
| /frameworks/base/docs/html/wear/ |
| index.jd | 90 Create enhanced user interaction and glanceable experiences.
|
| /frameworks/base/docs/html-intl/intl/es/distribute/googleplay/quality/ |
| auto.jd | 255 <td rowspan="2" id="interaction">
|
| /frameworks/base/docs/html-intl/intl/in/preview/features/ |
| notification-updates.jd | 181 // handled their interaction with the previous notification.
|
| /frameworks/base/graphics/java/android/graphics/drawable/ |
| AnimationDrawable.java | 143 * interaction, then you might want to call it from the
|
| /frameworks/base/media/java/android/media/tv/ |
| TvInputManager.java | 59 * interaction between applications and the selected TV inputs. You can retrieve an instance of
67 * system that manages interaction between all other parts. It is expressed as the client-side API
69 * manages the interaction across all processes.
76 * {@link TvRecordingClient} for further interaction such as watching and recording broadcast TV
[all...] |
