| /frameworks/base/core/res/res/drawable/ |
| jog_tab_left_generic.xml | 17 <!-- StateListDrawable used for buttons in the in-call onscreen touch UI. -->
|
| jog_tab_left_unlock.xml | 17 <!-- StateListDrawable used for buttons in the in-call onscreen touch UI. -->
|
| jog_tab_right_decline.xml | 17 <!-- StateListDrawable used for buttons in the in-call onscreen touch UI. -->
|
| jog_tab_right_generic.xml | 17 <!-- StateListDrawable used for buttons in the in-call onscreen touch UI. -->
|
| jog_tab_right_sound_off.xml | 17 <!-- StateListDrawable used for buttons in the in-call onscreen touch UI. -->
|
| jog_tab_right_sound_on.xml | 17 <!-- StateListDrawable used for buttons in the in-call onscreen touch UI. -->
|
| /frameworks/base/core/tests/coretests/src/android/widget/gridview/ |
| GridPaddingTest.java | 41 assertTrue("Not in touch mode", mGridView.isInTouchMode());
|
| /frameworks/base/core/tests/coretests/src/android/widget/layout/linear/ |
| LLOfButtons1.java | 29 * the transistion between touch and focus mode.
|
| /frameworks/base/core/tests/coretests/src/android/widget/listview/touch/ |
| ListTouchBottomGravityManyTest.java | 17 package android.widget.listview.touch;
31 * Touch tests for a list where all of the items do not fit on the screen, and the list
66 assertEquals("Selection still available after touch", -1,
86 assertEquals("Selection still available after touch", -1,
|
| ListTouchManyTest.java | 17 package android.widget.listview.touch;
31 * Touch tests for a list where all of the items do not fit on the screen.
63 assertEquals("Selection still available after touch", -1,
81 assertEquals("Selection still available after touch", -1,
|
| /frameworks/base/services/java/com/android/server/status/ |
| CloseDragHandle.java | 33 * Ensure that, if there is no target under us to receive the touch,
|
| /frameworks/base/test-runner/src/android/test/ |
| ActivityInstrumentationTestCase2.java | 93 // set initial touch mode
130 * Call this method before the first call to {@link #getActivity} to set the initial touch
133 * <p>If you do not call this, the touch mode will be false. If you call this after
140 * @param initialTouchMode true if the Activity should be placed into "touch mode" when started
|
| /packages/apps/DeskClock/res/drawable/ |
| btn_strip_trans_left.xml | 18 corners of the in-call onscreen touch UI. -->
|
| btn_strip_trans_middle.xml | 18 corners of the in-call onscreen touch UI. -->
|
| btn_strip_trans_right.xml | 18 corners of the in-call onscreen touch UI. -->
|
| incall_round_button.xml | 18 corners of the in-call onscreen touch UI. -->
|
| /packages/apps/Phone/res/drawable/ |
| incall_button.xml | 17 <!-- StateListDrawable used for buttons in the in-call onscreen touch UI. -->
|
| incall_round_button.xml | 18 corners of the in-call onscreen touch UI. -->
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/resources/manager/ |
| Resource.java | 35 public final void touch() { method in class:Resource
|
| /external/bluetooth/bluez/doc/ |
| gtk-doc.make | 68 test -f $$i || touch $$i ; \
71 touch scan-build.stamp
82 touch tmpl-build.stamp
98 touch sgml-build.stamp
114 touch html-build.stamp
|
| /frameworks/base/core/java/android/widget/ |
| RatingBar.java | 29 * stars. The user can touch/drag or use arrow keys to set the rating when using
54 * includes changes that were initiated by the user through a touch gesture
65 * lifting the touch.
71 * touch gesture or arrow key/horizontal trackbell movement.
108 // A touch inside a star fill up to that fractional area (slightly more
|
| /packages/apps/Phone/src/com/android/phone/ |
| InCallTouchUi.java | 42 * In-call onscreen touch UI elements, used on some platforms.
45 * non-touch-sensitive parts of the in-call UI (i.e. the call card).
92 // Overall enabledness of the "touch UI" features
112 // The various touch UI features are enabled on a per-product
117 if (DBG) log("- incoming call touch UI: "
120 if (DBG) log("- regular in-call touch UI: "
277 // Ok, the in-call touch UI is available on this platform,
282 if (DBG) log("- updateState: NOT OK to show touch UI; disabling...");
293 "'Incoming' and 'in-call' touch controls visible at the same time!");
343 // in-call touch UI is disabled, like during an OTA call or if th
[all...] |
| /external/webkit/WebCore/plugins/android/ |
| PluginViewAndroid.cpp | 55 #include "Touch.h"
201 evt.data.touch.action = kDown_ANPTouchAction;
203 evt.data.touch.action = kUp_ANPTouchAction;
205 evt.data.touch.action = kMove_ANPTouchAction;
207 evt.data.touch.action = kCancel_ANPTouchAction;
209 evt.data.touch.action = kLongPress_ANPTouchAction;
211 evt.data.touch.action = kDoubleTap_ANPTouchAction;
215 evt.data.touch.modifiers = 0; // todo
218 // co-ordinates as there is no touch in touches anymore.
219 TouchList* touches = (evt.data.touch.action == kUp_ANPTouchActio
[all...] |
| /frameworks/base/docs/html/guide/practices/ui_guidelines/ |
| menu_design.jd | 14 <li>The commands on the Context menu that appears when you touch & hold on an item should be duplicated on the activity you get to by a normal press on that item.
49 <li><a href="http://android-developers.blogspot.com/2008/12/touch-mode.html">Touch mode</a></li>
74 selected item. It is typically invoked by a user's touch & hold
170 A user can touch & hold on content on the screen to
180 For example, in an email message list, a user can touch & hold on
186 A user can also touch & hold a <em>location</em> on the screen to
187 access a Context menu. An example is when the user does touch & hold
197 In the above example, if the user performs touch & hold on the contact
204 A normal touch on an item in the content activates the most intuitiv
[all...] |
| /packages/inputmethods/LatinIME/java/src/com/android/inputmethod/latin/ |
| LatinKeyboardView.java | 59 * Whether multi-touch disambiguation needs to be disabled for any reason. There are 2 reasons
60 * for this to happen - (1) if a real multi-touch event has occured and (2) we've opened an
64 /** The distance threshold at which we start treating the touch session as a multi-touch */
112 * that could be due to a multi-touch being treated as a move by the firmware or hardware.
127 // Real multi-touch event? Stop looking for sudden jumps
132 // If UP, reset the multi-touch flag
170 // the user is releasing the touch on the second key.
256 // Stop processing multi-touch errors
|
