/frameworks/base/docs/html/training/graphics/opengl/ |
D | touch.jd | 37 The key to making your OpenGL ES application touch interactive is expanding your implementation of 39 android.opengl.GLSurfaceView#onTouchEvent onTouchEvent()} to listen for touch events.</p> 41 <p>This lesson shows you how to listen for touch events to let users rotate an OpenGL ES object.</p> 46 <p>In order to make your OpenGL ES application respond to touch events, you must implement the 55 // MotionEvent reports input details from the touch screen 57 // interested in events where the touch position changed. 120 <p>To apply the rotation generated by touch input, comment out the code that generates an angle and 121 add {@code mAngle}, which contains the touch input generated angle:</p> 142 <img src="{@docRoot}images/opengl/ogl-triangle-touch.png"> 144 <strong>Figure 1.</strong> Triangle being rotated with touch input (circle shows touch
|
D | index.jd | 42 setup, drawing objects, moving drawn elements and responding to touch input.</p> 73 <dt><b><a href="touch.html">Responding to Touch Events</a></b></dt>
|
/frameworks/base/core/tests/coretests/src/com/android/internal/util/ |
D | FileRotatorTest.java | 210 touch("another_rotator.1024"); in testOtherFilesAndMalformed() 211 touch("another_rotator.1024-2048"); in testOtherFilesAndMalformed() 215 touch("rotator"); in testOtherFilesAndMalformed() 216 touch("rotator..."); in testOtherFilesAndMalformed() 217 touch("rotator.-"); in testOtherFilesAndMalformed() 218 touch("rotator.---"); in testOtherFilesAndMalformed() 219 touch("rotator.a-b"); in testOtherFilesAndMalformed() 220 touch("rotator_but_not_actually"); in testOtherFilesAndMalformed() 370 private void touch(String... names) throws IOException { in touch() method in FileRotatorTest
|
/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? 25 … android:<a href="#touch">reqTouchScreen</a>=["undefined" | "notouch" | "stylus" | 41 requires a five-way navigation control, a touch screen that can be operated 142 <dt><a name="touch"></a>{@code android:reqTouchScreen}</dt> 143 <dd>The type of touch screen the application requires, if any at all. 152 <td>The application doesn't require a touch screen. 153 (The touch screen requirement is undefined.) 157 <td>The application doesn't require a touch screen.</td> 160 <td>The application requires a touch screen that's operated with a stylus.</td> [all …]
|
D | uses-feature-element.jd | 714 input is be something like a d-pad, and generally not through touch or a 721 <td>The application uses basic touch interaction events, such as "click down", "click 724 only if it offers an emulated touchscreen ("fake touch" interface), or better. A device that offers 725 a fake touch interface provides a user input system that emulates a subset of touchscreen 727 touch interface. If your application requires basic point and click interaction (in other 729 Because this is the minimum level of touch interaction, your app will also be compatible with 730 devices that offer more complex touch interfaces.</p> 733 devices that provide a fake touch interface, you must also explicitly declare that a touch screen is 741 <td>The application performs distinct tracking of two or more "fingers" on a fake touch 744 only if it supports touch emulation for events that supports distinct tracking of two or more [all …]
|
/frameworks/base/data/keyboards/ |
D | qwerty.idc | 19 touch.deviceType = touchScreen 20 touch.orientationAware = 1
|
D | qwerty2.idc | 19 touch.deviceType = touchScreen 20 touch.orientationAware = 1
|
/frameworks/base/docs/html/guide/topics/ui/ |
D | ui-events.jd | 55 (when in touch mode), or focuses upon the item with the navigation-keys or trackball and 59 This is called when the user either touches and holds the item (when in touch mode), or 70 …This is called when the user performs an action qualified as a touch event, including a press, a r… 180 …<li><code>{@link android.view.View#onTouchEvent}</code> - Called when a touch screen motion event… 189 … android.app.Activity} to intercept all touch events before they are dispatched to the window.</li> 195 upon a parent View to indicate that it should not intercept touch events with <code>{@link 203 what will accept input. If the device has touch capabilities, however, and the user 206 for interaction named "touch mode." 209 For a touch-capable device, once the user touches the screen, the device 210 will enter touch mode. From this point onward, only Views for which [all …]
|
/frameworks/base/docs/html/tools/help/ |
D | MonkeyDevice.jd | 42 <code><a href="#press">press()</a></code> or <code><a href="#touch">touch()</a> 52 <code><a href="#press">press()</a></code> or <code><a href="#touch">touch()</a> 62 <code><a href="#press">press()</a></code> or <code><a href="#touch">touch()</a> 115 Simulates a drag gesture (touch, hold, and move) on this device's screen. 333 <a href="#touch">touch</a> 340 Sends a touch event specified by type to the screen location specified 354 <a href="#touch">type</a> 375 <a href="#touch">wake</a> 399 <code><a href="#press">touch()</a></code> value. 418 <code><a href="#press">touch()</a></code> value. [all …]
|
/frameworks/base/core/tests/coretests/src/android/widget/listview/touch/ |
D | ListGetSelectedViewTest.java | 17 package android.widget.listview.touch;
|
D | ListTouchTest.java | 17 package android.widget.listview.touch;
|
D | ListTouchBottomGravityTest.java | 17 package android.widget.listview.touch;
|
D | ListOfTouchablesTest.java | 17 package android.widget.listview.touch;
|
D | ListSetSelectionTest.java | 17 package android.widget.listview.touch;
|
D | ListTouchBottomGravityManyTest.java | 17 package android.widget.listview.touch;
|
/frameworks/base/docs/html/guide/practices/ui_guidelines/ |
D | menu_design.jd | 47 …<li>The commands on the Context menu that appears when you touch & hold on an item should be d… 82 <li><a href="http://android-developers.blogspot.com/2008/12/touch-mode.html">Touch mode</a></li> 107 selected item. It is typically invoked by a user's touch & hold 203 A user can touch & hold on content on the screen to 213 For example, in an email message list, a user can touch & hold on 219 A user can also touch & hold a <em>location</em> on the screen to 220 access a Context menu. An example is when the user does touch & hold 230 In the above example, if the user performs touch & hold on the contact 237 A normal touch on an item in the content activates the most intuitive 337 <a href="http://android-developers.blogspot.com/2008/12/touch-mode.html">Touch mode</a>. [all …]
|
/frameworks/base/docs/html/tools/testing/ |
D | activity_testing.jd | 43 <a href="#NotouchMode">Turning off touch mode</a> 111 User interface interaction: You use instrumentation to send keystrokes or touch events 231 to help you handle actions that run in the UI thread, touch screen and keyboard events, and home 297 <h3 id="NotouchMode">Turning off touch mode</h3> 300 touch mode. If you do not do this, the key events are ignored. 303 To turn off touch mode, you invoke 307 can't invoke the touch mode method from a test method that is annotated with 308 <code>@UIThread</code>. Instead, invoke the touch mode method from <code>setUp()</code>. 348 a view hierarchy can touch its views.
|
/frameworks/base/core/tests/coretests/src/android/widget/gridview/touch/ |
D | GridTouchSetSelectionTest.java | 17 package android.widget.gridview.touch;
|
D | GridTouchStackFromBottomManyTest.java | 17 package android.widget.gridview.touch;
|
D | GridTouchStackFromBottomTest.java | 17 package android.widget.gridview.touch;
|
/frameworks/base/tests/touchlag/ |
D | touchlag.cpp | 250 TouchEvents touch; in main() local 276 touch.getMostRecentPosition(&x, &y); in main()
|
/frameworks/base/docs/html/training/custom-views/ |
D | making-interactive.jd | 62 most common input event in the Android system is <em>touch</em>, which triggers {@link 73 <p>Touch events by themselves are not particularly useful. Modern touch UIs define interactions in 75 such as tapping, pulling, pushing, flinging, and zooming. To convert raw touch events into 116 your {@link android.view.GestureDetector} to interpret the touch events you receive in {@link 133 <p>When you pass {@link android.view.GestureDetector#onTouchEvent onTouchEvent()} a touch event that
|
/frameworks/base/docs/html/about/versions/ |
D | android-3.1-highlights.jd | 78 touch-hold interval to meet their needs.</p> 116 and recently used apps, then touch a thumbnail to jump back into that task.</p> 166 point, by touch-hold of the access point in Settings. The browser uses the HTTP 213 single touch. The app also copies the pictures to local storage and provides an 224 touch-targeting. Additionally, users can create a larger viewing area for grids 246 can touch Email icon at the top of the widget to cycle through labels such as 327 Hat Y, rotation, throttle, pressure, size, touch, tool, orientation, and others.
|
D | android-3.0.jd | 502 scroll through values or touch again to directly edit the current value. It also allows you to map 697 <h3>Split touch events</h3> 699 <p>Previously, only a single view could accept touch events at one time. Android 3.0 700 adds support for splitting touch events across views and even windows, so different views can accept 701 simultaneous touch events.</p> 703 <p>Split touch events is enabled by default when an application targets 709 <p>However, the following properties allow you to disable split touch events across views inside 714 allows you to disable split touch events that occur between child views in a layout. For example: 720 <p>This way, child views in the linear layout cannot split touch events—only one view can 721 receive touch events at a time.</p> [all …]
|
/frameworks/base/docs/html/design/building-blocks/ |
D | tabs.jd | 39 <p>Fixed tabs display all items concurrently. To navigate to a different view, touch the tab.</p>
|