/frameworks/base/data/keyboards/ |
D | qwerty2.idc | 16 # Emulator keyboard configuration file #2. 22 keyboard.layout = qwerty 23 keyboard.characterMap = qwerty2 24 keyboard.orientationAware = 1 25 keyboard.builtIn = 1
|
D | qwerty.idc | 16 # Emulator keyboard configuration file #1. 22 keyboard.layout = qwerty 23 keyboard.characterMap = qwerty 24 keyboard.orientationAware = 1 25 keyboard.builtIn = 1
|
D | qwerty.kl | 16 # Emulator keyboard layout #1. 18 # This file is no longer used as the platform's default keyboard layout. 110 # On an AT keyboard: ESC, F10
|
D | Vendor_046d_Product_c532.kl | 16 # Logitech Revue Wireless keyboard 19 # - The GRAVE key is emulated by the keyboard.
|
/frameworks/base/docs/html/samples/new/ |
D | index.jd | 38 <h3 id="img-kbd-app">Image keyboard app sample</h3> 57 <a href="/samples/CommitContentSampleApp/index.html">Image keyboard app sample</a> 60 <h3 id="img-kbd-ime">Image keyboard IME sample</h3> 69 "/preview/image-keyboard.html">custom image keyboard</a> using the <a href= 73 This keyboard will be displayed inside compatible apps (also using the Commit 79 <a href="/samples/CommitContentSampleIME/index.html">Image keyboard IME sample</a>
|
/frameworks/base/docs/html/training/keyboard-input/ |
D | navigation.jd | 26 physical keyboards attached to the device. A keyboard offers not only a convenient 31 keyboard accessories.</p> 34 you optimize your app to support interaction through a keyboard. This lesson describes 35 how you can better support navigation with a keyboard.</p> 49 <p>It's possible that users can already navigate your app using a keyboard, because the 54 control devices such as a D-pad or keyboard and each widget glows or otherwise changes its 59 <li>Install your app on a device that offers a hardware keyboard. 60 <p>If you don't have a hardware device with a keyboard, connect a Bluetooth keyboard 61 or a USB keyboard (though not all devices support USB accessories).</p> 75 (arrow keys on the keyboard) to navigate your app. [all …]
|
D | commands.jd | 21 element and the user has a hardware keyboard attached, all 23 or directly handle the keyboard input yourself, you can do so by implementing callback methods 34 <p class="note"><strong>Note:</strong> When handling keyboard events with the {@link 35 android.view.KeyEvent} class and related APIs, you should expect that such keyboard 36 events come only from a hardware keyboard. You should never rely on receiving key events 37 for any key on a soft input method (an on-screen keyboard).</p> 49 <p>For example, this implementation responds to some keyboard keys to control a game:</p>
|
D | index.jd | 21 <p>The Android system shows an on-screen keyboard—known as a 30 through an attached keyboard.</p> 48 <dd>Learn how to verify that users can navigate your app using a keyboard 52 <dd>Learn how to respond directly to keyboard input for user actions.
|
/frameworks/base/core/java/android/content/res/ |
D | Configuration.java | 415 public int keyboard; field in Configuration 760 keyboard = o.keyboard; in setTo() 875 switch (keyboard) { in toString() 880 default: sb.append(" keys="); sb.append(keyboard); break; in toString() 927 keyboard = KEYBOARD_UNDEFINED; in setToDefaults() 999 if (delta.keyboard != KEYBOARD_UNDEFINED in updateFrom() 1000 && keyboard != delta.keyboard) { in updateFrom() 1002 keyboard = delta.keyboard; in updateFrom() 1146 if (delta.keyboard != KEYBOARD_UNDEFINED in diff() 1147 && keyboard != delta.keyboard) { in diff() [all …]
|
/frameworks/base/core/jni/ |
D | android_content_res_Configuration.cpp | 36 jfieldID keyboard; member 54 out->keyboard = env->GetIntField(clazz, gConfigurationClassInfo.keyboard); in android_Configuration_getFromJava() 84 gConfigurationClassInfo.keyboard = GetFieldIDOrDie(env, clazz, "keyboard", "I"); in register_android_content_res_Configuration()
|
/frameworks/base/docs/html/guide/topics/ui/controls/ |
D | text.jd | 34 multi-line. Touching a text field places the cursor and automatically displays the keyboard. In 64 keyboard to optimize its layout for frequently used characters.</p> 66 <p>You can specify the type of keyboard you want for your {@link android.widget.EditText} object 88 <dd>Normal text keyboard.</dd> 90 <dd>Normal text keyboard with the @ character.</dd> 92 <dd>Normal text keyboard with the / character.</dd> 103 android:inputType}</a> also allows you to specify certain keyboard behaviors, such as whether to 107 android:inputType}</a> attribute allows bitwise combinations so you can specify both a keyboard 110 <p>Here are some of the common input type values that define keyboard behaviors:</p> 114 <dd>Normal text keyboard that capitalizes the first letter for each new sentence.</dd> [all …]
|
/frameworks/base/docs/html/guide/topics/manifest/ |
D | uses-configuration-element.jd | 9 keyboard / navigation control / touch screen." Dianne says that that's what they mean and 11 keyboard / navigation control / touch screen to work." But then what does "undefined" mean? 31 For example, an application might specify that it requires a physical keyboard 65 <dd>Whether or not the application requires a hardware keyboard — 69 <dd>The type of keyboard the application requires, if any at all. 71 keyboards. If a hardware keyboard of a certain type is required, 85 <td>The application does not require a keyboard. 86 (A keyboard requirement is not defined.) 90 <td>The application does not require a keyboard.</td> 93 <td>The application requires a standard QWERTY keyboard.</td>
|
/frameworks/base/native/android/ |
D | configuration.cpp | 75 return config->keyboard; in AConfiguration_getKeyboard() 167 void AConfiguration_setKeyboard(AConfiguration* config, int32_t keyboard) { in AConfiguration_setKeyboard() argument 168 config->keyboard = keyboard; in AConfiguration_setKeyboard()
|
/frameworks/base/packages/DocumentsUI/tests/src/com/android/documentsui/ |
D | RenameDocumentUiTest.java | 97 bots.keyboard.pressEnter(); in testRenameFile_Enter() 129 bots.keyboard.pressEnter(); in testRenameDir() 144 bots.keyboard.pressEnter(); in testRename_NameExists()
|
D | ActivityTest.java | 176 public final KeyboardBot keyboard; field in ActivityTest.Bots 182 this.keyboard = new KeyboardBot(device, context, TIMEOUT); in Bots()
|
/frameworks/base/core/tests/coretests/src/android/app/activity/ |
D | ActivityManagerTest.java | 102 assertEquals(config.reqKeyboardType, vconfig.keyboard); in testGetDeviceConfigurationInfo() 108 if (vconfig.keyboard != Configuration.KEYBOARD_UNDEFINED) { in testGetDeviceConfigurationInfo()
|
/frameworks/base/packages/SystemUI/src/com/android/systemui/keyboard/ |
D | BluetoothDialog.java | 17 package com.android.systemui.keyboard;
|
/frameworks/base/docs/html/tv/adt-1/ |
D | index.jd | 120 <strong>How do I use the gamepad with the on-screen keyboard?</strong> 135 <strong>Can I connect a USB keyboard or mouse to ADT-1?</strong> 137 <p>Yes, you can connect a USB keyboard or mouse to the USB port on the back of ADT-1. 141 these devices. If a particular keyboard or mouse does not work, try a different model. 240 <strong>Why doesn't the on-screen keyboard come up?</strong> 242 <p>Enable the keyboard in the device Settings. Go to <strong>Settings > Preferences > 243 Keyboard > Current keyboard</strong> and choose <strong>Leanback keyboard</strong>. 288 start a voice search, or use the keyboard to input text using this app.</p>
|
/frameworks/base/docs/html/guide/topics/text/ |
D | creating-input-method.jd | 2 page.tags=ime,keyboard,inputmethodservice 123 important for handling keyboard characters. 148 An extension of {@link android.view.View} that renders a keyboard and responds to user 149 input events. The keyboard layout is specified by an instance of 184 traditional QWERTY keyboard, 424 <li>An input mode such as voice, keyboard, or handwriting</li> 427 keyboard layouts. 431 Basically, the mode can be any text such as "keyboard", "voice", and so forth. A subtype can 444 subtypes: a keyboard subtype for the US English locale, and another keyboard subtype for the 454 android:imeSubtypeMode="keyboard" [all …]
|
/frameworks/base/docs/html/wear/preview/features/ |
D | ime.jd | 92 which causes the app to dismiss the keyboard and continue on to the next step 112 password mode, make sure that your keyboard is optimized for single key press 114 Most importantly, keyboard in password mode should support ASCII symbols 116 <a href="{@docRoot}training/keyboard-input/style.html">Specifying The Input Method Type</a>.
|
/frameworks/support/core-ui/ |
D | NOTICES.md | 11 - The concept of keyboard and accessibility focus have been clarified. As a result, the
|
/frameworks/base/core/java/android/inputmethodservice/ |
D | Keyboard.java | 276 private Keyboard keyboard; field in Keyboard.Key 315 keyboard = parent.parent; in Key() 342 keyboard.mDisplayWidth, parent.defaultWidth); in Key() 345 keyboard.mDisplayHeight, parent.defaultHeight); in Key() 348 keyboard.mDisplayWidth, parent.defaultHorizontalGap); in Key()
|
D | KeyboardView.java | 471 public void setKeyboard(Keyboard keyboard) { in setKeyboard() argument 477 mKeyboard = keyboard; in setKeyboard() 484 computeProximityThreshold(keyboard); in setKeyboard() 617 private void computeProximityThreshold(Keyboard keyboard) { in computeProximityThreshold() argument 618 if (keyboard == null) return; in computeProximityThreshold() 1135 Keyboard keyboard; in onLongPress() local 1137 keyboard = new Keyboard(getContext(), popupKeyboardId, in onLongPress() 1140 keyboard = new Keyboard(getContext(), popupKeyboardId); in onLongPress() 1142 mMiniKeyboard.setKeyboard(keyboard); in onLongPress()
|
/frameworks/base/packages/InputDevices/res/raw/ |
D | keyboard_layout_english_us.kcm | 16 # English (US) keyboard layout. 17 # Unlike the default (generic) keyboard layout, English (US) does not contain any
|
D | keyboard_layout_english_us_colemak.kcm | 16 # English (US), Colemak keyboard layout. 17 # Unlike the default (generic) keyboard layout, English (US) does not contain any
|