| /frameworks/base/packages/SystemUI/src/com/android/systemui/stackdivider/ |
| D | DividerHandleView.java | 89 public void setTouching(boolean touching, boolean animate) { in setTouching() argument
90 if (touching == mTouching) { in setTouching()
98 if (touching) { in setTouching()
107 animateToTarget(touching ? mCircleDiameter : mWidth, in setTouching()
108 touching ? mCircleDiameter : mHeight, touching); in setTouching()
110 mTouching = touching; in setTouching()
113 private void animateToTarget(int targetWidth, int targetHeight, boolean touching) { in animateToTarget() argument
120 mAnimator.setDuration(touching in animateToTarget()
123 mAnimator.setInterpolator(touching in animateToTarget()
|
| D | DividerView.java | 347 public boolean startDragging(boolean animate, boolean touching) { in startDragging() argument
349 if (touching) { in startDragging()
355 if (touching) { in startDragging()
|
| /frameworks/base/docs/html/training/beam-files/ |
| D | index.jd | 33 touching devices. In response, Android Beam file transfer automatically copies files from one
|
| /frameworks/base/docs/html/design/handhelds/ |
| D | index.jd | 33 <p>Access the entire collection of apps and widgets by touching the All Apps button at the center of
58 <p>Switch to an app by touching it. Remove an item by swiping left or right.</p>
|
| /frameworks/base/docs/html/design/patterns/ |
| D | navigation.jd | 183 new Task A (see figure below). After navigating through the Play Store and touching a promoted book
194 <p>From the compose activity, sending the message or touching the Back button returns the user to
200 <p>However, by touching Up from the compose activity, the user indicates a desire to remain within
202 always rooted to Home, so touching Back from the conversation list returns there.</p>
|
| D | compatibility.jd | 30 <p>Users access the action overflow by touching it in the action bar.</p>
|
| D | buttons.jd | 88 and showing app controls. For example, if touching anywhere on the screen
|
| D | fullscreen.jd | 88 and showing app controls. For example, if touching anywhere on the screen
|
| D | actionbar.jd | 262 <li>Select additional elements by touching them.</li>
|
| /frameworks/base/docs/html/training/system-ui/ |
| D | navigation.jd | 76 <li>With this approach, touching anywhere on the screen causes the navigation bar (and
|
| D | immersive.jd | 220 manually toggle the visibility of the system bars by touching your content.
|
| /frameworks/base/docs/html/training/implementing-navigation/ |
| D | descendant.jd | 55 …on from the Launcher (the device home screen). It would be confusing if touching your application …
|
| D | nav-drawer.jd | 299 open and close it by touching the app icon. And the app icon should also indicate the presence of
|
| /frameworks/base/docs/html/guide/practices/ui_guidelines/ |
| D | menu_design.jd | 148 button or touching outside the menu also works.) Note that how to invoke this
381 be available by the user touching the phone number itself when viewing contact details.
389 touching on an item in the content should activate the same command as touching
|
| D | activity_task_design.jd | 400 the user action of going Home and touching the Email icon launches the
421 following figure, the user starts email by touching the Email icon in
665 When the user takes an action on some data, such as touching a
669 So, the result of a user touching a mailto: link is an Intent object
681 This example of touching the mailto: link is shown in the following
946 started by the user touching an icon in <em>application
|
| D | icon_design_launcher_archive.jd | 45 <p>The user opens the Launcher by touching the icon at the bottom of the Home
47 applications. The user selects an application and opens it by touching the
|
| /frameworks/base/docs/html/distribute/tools/ |
| D | open-distribution.jd | 79 your app by touching the button.
|
| /frameworks/base/docs/html/guide/topics/ui/ |
| D | ui-events.jd | 200 begins interacting with the interface by touching it, then it is no longer necessary to
214 with the user interface without touching the screen.
|
| /frameworks/base/docs/html/training/gestures/ |
| D | viewgroup.jd | 177 operation, such as touching on-screen elements.</p>
|
| D | scale.jd | 82 pointer that is no longer touching the screen. If it is, the app selects a
|
| /frameworks/base/docs/html/training/wearables/notifications/ |
| D | creating.jd | 90 setContentIntent()} method by touching the notification. When this
|
| /frameworks/base/docs/html/ndk/guides/audio/ |
| D | output-latency.jd | 78 <li><strong>Touch latency</strong> is the time between a user touching the screen and that
|
| /frameworks/base/docs/html/training/design-navigation/ |
| D | descendant-lateral.jd | 158 …esented one at a time. Users are able to navigate to sibling screens by touching and dragging the …
|
| /frameworks/base/docs/html/distribute/essentials/quality/ |
| D | tv.jd | 32 control device to navigate and make selections rather than touching elements on screen. These
|
| /frameworks/base/docs/html/guide/topics/ui/accessibility/ |
| D | apps.jd | 150 button) of a directional controller has the same effect as touching a control that already has
257 android.view.View} control, make sure this event has the same effect as touching the view on the
|