/frameworks/support/v4/java/android/support/v4/view/ |
D | KeyEventCompat.java | 56 final int directional = left | right; in metaStateFilterDirectionalModifiers() local 57 final boolean wantLeftOrRight = (modifiers & directional) != 0; in metaStateFilterDirectionalModifiers() 63 return metaState & ~directional; in metaStateFilterDirectionalModifiers()
|
/frameworks/base/docs/html/training/accessibility/ |
D | testing.jd | 61 <li>All task workflows in the application can be easily navigated using directional controls and 73 without the use of a touch screen. Attempt to use only directional controls to accomplish the 74 primary tasks in the application. Use the keyboard and directional-pad (D-Pad) controls in the 85 directional controls to move focus between application layout elements.</li> 191 does not require screen elements to be focused using an directional controller, but listens for 216 <p>Focus navigation is the use of directional controls to navigate between the individual user 220 directional controls.</p> 223 does not have a directional controller. The <a href="{@docRoot}tools/help/emulator.html">Android 224 Emulator</a> provides a simulated directional controller that you can use to test navigation. You 225 can also use a software-based directional controller, such as the one provided by the
|
D | index.jd | 43 navigation with a keyboard or directional pad, set labels and fire events
|
D | accessible-app.jd | 190 <p>Also, attempt to navigate your application using a directional controller, 195 <p>Between the service providing feedback and the directional navigation through
|
/frameworks/base/docs/html/training/tv/start/ |
D | navigation.jd | 37 directional pad (D-pad) or arrow keys. This type of control limits movement to up, down, left, 43 The Android framework handles directional navigation between layout elements automatically, so 62 <h3 id="modify-d-pad-nav">Modifying directional navigation</h3> 65 The Android framework automatically applies a directional navigation scheme based on the 68 users to move through your layouts in a specific way, you can set up explicit directional
|
D | index.jd | 29 navigation that works with just a directional pad and a select button.
|
D | hardware.jd | 286 navigation using a directional pad (D-pad) on a TV remote control. For more information on
|
/frameworks/base/docs/html/guide/topics/manifest/ |
D | uses-configuration-element.jd | 36 <em>always</em> support input with a directional pad (d-pad) in order to assist sight-impaired 54 D-pad (directional pad), trackball, or other device. 57 If an application requires a directional control, but not a control of a 60 if it requires a particular type of directional control, it can ignore 120 <td>The application requires a D-pad (directional pad) for navigation.</td>
|
/frameworks/base/docs/html/guide/topics/ui/accessibility/ |
D | apps.jd | 20 <li><a href="#directional-control">Handling directional controller clicks</a></li> 69 reached with a directional controller, such as a trackball, D-pad (physical or virtual) or 77 and then try using your application using only directional controls. For more information on 140 directional controller. Directional controllers can be physical, such as a trackball, directional 147 <p>To ensure that users can navigate your application using only a directional controller, verify 150 button) of a directional controller has the same effect as touching a control that already has 151 focus. For information on testing directional controls, see 158 <p>A user interface element is reachable using directional controls when its 161 on the element using the directional controls and then interact with it. The user interface controls 182 <p>When users navigate in any direction using directional controls, focus is passed from one [all …]
|
D | index.jd | 51 directional-pad navigation. Android application developers can take advantage of these services to
|
D | checklist.jd | 66 your screen layouts using hardware-based or software directional controls (D-pads, trackballs, 83 using directional controls, and using eyes-free navigation with TalkBack enabled.
|
/frameworks/base/docs/html/training/game-controllers/ |
D | index.jd | 51 input elements on game controllers, including directional pad (D-pad)
|
D | controller-input.jd | 81 <dd>An object that describes directional 103 physical controls (gamepad buttons, directional pads, and 125 although most gamepads typically have directional controls.</li> 329 <p>The 4-way directional pad (D-pad) is a common physical control in many game 433 // Check that input comes from a device with directional pads.
|
/frameworks/base/docs/html/training/keyboard-input/ |
D | navigation.jd | 38 Supporting of directional navigation in your application is also important in ensuring that 40 to users who do not navigate using visual cues. Fully supporting directional navigation in your
|
/frameworks/base/core/java/android/view/ |
D | KeyEvent.java | 2166 final int directional = left | right; in metaStateFilterDirectionalModifiers() local 2167 final boolean wantLeftOrRight = (modifiers & directional) != 0; in metaStateFilterDirectionalModifiers() 2175 return metaState & ~directional; in metaStateFilterDirectionalModifiers()
|
/frameworks/base/docs/html/design/patterns/ |
D | accessibility.jd | 35 <p>Some users use hardware or software directional controllers (such as a D-pad, trackball, keyboar… 86 …>Settings > Accessibility</strong> and navigate your application using directional controls or eye…
|
/frameworks/base/docs/html/design/tv/ |
D | patterns.jd | 11 <p>Users typically navigate TV devices using a directional pad (D-Pad). This type of controller
|
/frameworks/base/docs/html/guide/topics/ui/ |
D | ui-events.jd | 197 When a user is navigating a user interface with directional keys or a trackball, it is 212 Any time a user hits a directional key or scrolls with a trackball, the device will
|
/frameworks/base/docs/html/guide/topics/ui/controls/ |
D | button.jd | 215 focused (when the button is highlighted using the trackball or directional
|
/frameworks/base/docs/html/training/tv/games/ |
D | index.jd | 83 Plan your control scheme around a directional pad (D-pad) control, since this control set is the
|
/frameworks/base/docs/html/about/versions/ |
D | android-4.3.jd | 78 <li><a href="#BiDi">Improved support for bi-directional text</a></li> 924 <h3 id="BiDi">Improved support for bi-directional text</h3> 975 previously may have been possible only with touch input or the device's directional pad.</p>
|
/frameworks/base/docs/html/guide/components/ |
D | aidl.jd | 155 <li>All non-primitive parameters require a directional tag indicating which way the data goes.
|
/frameworks/base/docs/html/training/testing/ui-testing/ |
D | uiautomator-testing.jd | 143 TalkBack and Explore by Touch, and try using your application using only directional controls.</li>
|
/frameworks/base/docs/html-intl/intl/in/guide/topics/resources/ |
D | providing-resources.jd | 754 … <li>{@code dpad}: Perangkat memiliki pad pengarah (directional pad / d-pad) untuk navigasi.</li> 756 …<li>{@code wheel}: Perangkat memiliki roda pengarah (directional wheel) untuk navigasi (tidak umum…
|
/frameworks/base/docs/html/guide/topics/text/ |
D | creating-input-method.jd | 403 example, you may want to consume the directional keys to navigate within your UI for candidate
|