Home
last modified time | relevance | path

Searched refs:keyboard (Results 1 – 25 of 137) sorted by relevance

123456

/frameworks/base/data/keyboards/
Dqwerty.idc16 # Emulator keyboard configuration file #1.
22 keyboard.layout = qwerty
23 keyboard.characterMap = qwerty
24 keyboard.orientationAware = 1
25 keyboard.builtIn = 1
Dqwerty2.idc16 # Emulator keyboard configuration file #2.
22 keyboard.layout = qwerty
23 keyboard.characterMap = qwerty2
24 keyboard.orientationAware = 1
25 keyboard.builtIn = 1
Dqwerty.kl16 # 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
DVendor_046d_Product_c532.kl16 # Logitech Revue Wireless keyboard
19 # - The GRAVE key is emulated by the keyboard.
/frameworks/base/core/java/android/content/res/
DConfiguration.java317 public int keyboard; field in Configuration
631 keyboard = o.keyboard; in setTo()
745 switch (keyboard) { in toString()
750 default: sb.append(" keys="); sb.append(keyboard); break; in toString()
796 keyboard = KEYBOARD_UNDEFINED; in setToDefaults()
865 if (delta.keyboard != KEYBOARD_UNDEFINED in updateFrom()
866 && keyboard != delta.keyboard) { in updateFrom()
868 keyboard = delta.keyboard; in updateFrom()
1011 if (delta.keyboard != KEYBOARD_UNDEFINED in diff()
1012 && keyboard != delta.keyboard) { in diff()
[all …]
/frameworks/base/docs/html/training/keyboard-input/
Dnavigation.jd26 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 …]
Dcommands.jd21 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>
Dindex.jd21 <p>The Android system shows an on-screen keyboard&mdash;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/jni/
Dandroid_content_res_Configuration.cpp34 jfieldID keyboard; member
52 out->keyboard = env->GetIntField(clazz, gConfigurationClassInfo.keyboard); in android_Configuration_getFromJava()
96 GET_FIELD_ID(gConfigurationClassInfo.keyboard, clazz, in register_android_content_res_Configuration()
/frameworks/base/docs/html/guide/topics/ui/controls/
Dtext.jd34 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/
Duses-configuration-element.jd9 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 &mdash;
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>
Dactivity-element.jd14 "touchscreen", "keyboard", "keyboardHidden",
227 <td>"{@code keyboard}"</td>
228 <td>The keyboard type has changed &mdash; for example, the user has
229 plugged in an external keyboard.</td>
232 <td>The keyboard accessibility has changed &mdash; for example, the
233 user has revealed the hardware keyboard.</td>
975 the on-screen soft keyboard. The setting for this attribute affects two
979 <li>The state of the soft keyboard &mdash; whether it is hidden or visible
983 resized smaller to make room for the soft keyboard or whether its contents
985 the soft keyboard.</li>
[all …]
/frameworks/base/native/android/
Dconfiguration.cpp75 return config->keyboard; in AConfiguration_getKeyboard()
163 void AConfiguration_setKeyboard(AConfiguration* config, int32_t keyboard) { in AConfiguration_setKeyboard() argument
164 config->keyboard = keyboard; in AConfiguration_setKeyboard()
/frameworks/base/core/tests/coretests/src/android/app/activity/
DActivityManagerTest.java102 assertEquals(config.reqKeyboardType, vconfig.keyboard); in testGetDeviceConfigurationInfo()
108 if (vconfig.keyboard != Configuration.KEYBOARD_UNDEFINED) { in testGetDeviceConfigurationInfo()
/frameworks/base/docs/html/tv/adt-1/
Dindex.jd119 <strong>How do I use the gamepad with the on-screen keyboard?</strong>
134 <strong>Can I connect a USB keyboard or mouse to ADT-1?</strong>
136 <p>Yes, you can connect a USB keyboard or mouse to the USB port on the back of ADT-1.
140 these devices. If a particular keyboard or mouse does not work, try a different model.
239 <strong>Why doesn't the on-screen keyboard come up?</strong>
241 <p>Enable the keyboard in the device Settings. Go to <strong>Settings &gt; Preferences &gt;
242 Keyboard &gt; Current keyboard</strong> and choose <strong>Leanback keyboard</strong>.
295 start a voice search, or use the keyboard to input text using this app.</p>
/frameworks/base/docs/html/guide/topics/text/
Dcreating-input-method.jd2 page.tags=ime,keyboard,inputmethodservice
131 packages. The {@link android.view.KeyEvent} class is important for handling keyboard
165 An extension of {@link android.view.View} that renders a keyboard and
167 input events. The keyboard layout is specified by an instance of
211 traditional QWERTY keyboard,
496 <li>An input mode such as voice, keyboard, or handwriting</li>
500 keyboard layouts.
504 Basically, the mode can be any text such as "keyboard", "voice", and so
523 subtypes: a keyboard subtype for the US English locale, and another
524 keyboard subtype for the
[all …]
/frameworks/base/docs/html/design/building-blocks/
Dtext-fields.jd13 Touching a text field places the cursor and automatically displays the keyboard. In addition to
38 what kind of characters are allowed inside the field, and may prompt the virtual keyboard to
Dpickers.jd13 up/down arrow buttons, it's possible to set the desired value from the keyboard or via a swipe
/frameworks/base/core/java/android/inputmethodservice/
DKeyboard.java275 private Keyboard keyboard; field in Keyboard.Key
314 keyboard = parent.parent; in Key()
341 keyboard.mDisplayWidth, parent.defaultWidth); in Key()
344 keyboard.mDisplayHeight, parent.defaultHeight); in Key()
347 keyboard.mDisplayWidth, parent.defaultHorizontalGap); in Key()
DKeyboardView.java461 public void setKeyboard(Keyboard keyboard) { in setKeyboard() argument
467 mKeyboard = keyboard; in setKeyboard()
474 computeProximityThreshold(keyboard); in setKeyboard()
607 private void computeProximityThreshold(Keyboard keyboard) { in computeProximityThreshold() argument
608 if (keyboard == null) return; in computeProximityThreshold()
1124 Keyboard keyboard; in onLongPress() local
1126 keyboard = new Keyboard(getContext(), popupKeyboardId, in onLongPress()
1129 keyboard = new Keyboard(getContext(), popupKeyboardId); in onLongPress()
1131 mMiniKeyboard.setKeyboard(keyboard); in onLongPress()
/frameworks/base/packages/InputDevices/res/raw/
Dkeyboard_layout_english_us.kcm16 # English (US) keyboard layout.
17 # Unlike the default (generic) keyboard layout, English (US) does not contain any
Dkeyboard_layout_english_us_colemak.kcm16 # English (US), Colemak keyboard layout.
17 # Unlike the default (generic) keyboard layout, English (US) does not contain any
Dkeyboard_layout_english_us_dvorak.kcm16 # English (US), Dvorak keyboard layout.
17 # Unlike the default (generic) keyboard layout, English (US) does not contain any
/frameworks/base/tools/aapt/
DAaptConfig.cpp601 if (out) out->keyboard = out->KEYBOARD_ANY; in parseKeyboard()
604 if (out) out->keyboard = out->KEYBOARD_NOKEYS; in parseKeyboard()
607 if (out) out->keyboard = out->KEYBOARD_QWERTY; in parseKeyboard()
610 if (out) out->keyboard = out->KEYBOARD_12KEY; in parseKeyboard()
/frameworks/base/tests/ImfTest/tests/src/com/android/imftest/samples/
DImfBaseTestCase.java65 int keyboardType = mTargetActivity.getResources().getConfiguration().keyboard; in setUp()

123456