| /platform_testing/tests/functional/settingstests/src/com/android/settings/functional/ |
| AboutPhoneSettingsTests.java | 208 @MediumTest // UI interaction
213 @MediumTest // UI interaction
|
| /frameworks/base/core/java/android/view/accessibility/ |
| AccessibilityInteractionClient.java | 40 * This class is a singleton that performs accessibility interaction
64 * interaction client through which all interactions occur and the latter is
545 * @param interactionId The interaction id to match the result with the request.
574 * @param interactionId The interaction id to match the result with the request.
623 * @param interactionId The interaction id to match the result with the request.
661 * @param interactionId The interaction id to match the result with the request.
[all...] |
| /frameworks/base/docs/html/about/versions/ |
| android-3.0-highlights.jd | 62 <p>Android 3.0 is a new version of the Android platform that is specifically optimized for devices with larger screen sizes, particularly tablets. It introduces a brand new, truly virtual and ?holographic? UI design, as well as an elegant, content-focused interaction model.</p>
66 <p>The new UI brings fresh paradigms for interaction, navigation, and customization and makes them available to all applications — even those built for earlier versions of the platform. Applications written for Android 3.0 are able to use an extended set of UI objects, powerful graphics, and media capabilities to engage users in new ways.</p>
153 <p>The Android 3.0 platform is designed specially to meet the unique needs of applications on devices with larger screen sizes. It offers all of the tools developers need to create incredible visual and interaction experiences on these devices.</p>
190 <p>Home screen widgets are popular with users because they offer fast access to application-specific data directly from the home screen. Android 3.0 lets developers take home screen widgets to the next level, offering more types of content and new modes of interaction with users. Developers can now use more standard UI widget types home screen widgets, including widgets that let users flip through collections of content as 3D stacks, grids, or lists. Users can interact with the home screen widgets in new ways, such as by using touch gestures to scroll and flip the content displayed in a widget. </p>
210 <p>The platform offers convenient new interaction modes that developers can use. For managing collections of items in lists or grids, developers can offer a new multiselect mode that lets users choose multiple items for an action. Developers can also use a new system-wide Clipboard to let users easily copy any type of data into and out of their applications. To make it easier for users to manage and organize files, developers can now add drag-and-drop interaction through a DragEvent framework.</p>
|
| /frameworks/base/docs/html/reference/android/support/test/espresso/ |
| ViewInteraction.html | 262 Each interaction is associated with a view identified by a view matcher. All view actions and
408 failurehandler for this particular interaction.
764 <td width="100%">this interaction for further perform/verification calls.
842 <td width="100%">this interaction for further perform/verification calls.
867 failurehandler for this particular interaction.</p>
881 <td width="100%">this interaction for further perform/verification calls.
|
| /external/deqp/android/cts/master/ |
| gles3-multisample.txt | [all...] |
| /external/deqp/android/cts/mnc/ |
| gles3-565-no-depth-no-stencil.txt | [all...] |
| gles3-multisample.txt | [all...] |
| /prebuilts/gdb/darwin-x86/lib/python2.7/ |
| pdb.py | 52 # Interaction prompt line will separate file and call info from code
148 self.interaction(frame, None)
158 self.interaction(frame, None)
164 Returns True if the normal interaction function must be called,
190 self.interaction(frame, None)
203 self.interaction(frame, exc_traceback)
205 # General interaction function
207 def interaction(self, frame, traceback): member in class:Pdb
[all...] |
| /prebuilts/gdb/linux-x86/lib/python2.7/ |
| pdb.py | 52 # Interaction prompt line will separate file and call info from code
148 self.interaction(frame, None)
158 self.interaction(frame, None)
164 Returns True if the normal interaction function must be called,
190 self.interaction(frame, None)
203 self.interaction(frame, exc_traceback)
205 # General interaction function
207 def interaction(self, frame, traceback): member in class:Pdb
[all...] |
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/ |
| pdb.py | 52 # Interaction prompt line will separate file and call info from code
148 self.interaction(frame, None)
158 self.interaction(frame, None)
164 Returns True if the normal interaction function must be called,
190 self.interaction(frame, None)
203 self.interaction(frame, exc_traceback)
205 # General interaction function
207 def interaction(self, frame, traceback): member in class:Pdb
[all...] |
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/ |
| pdb.py | 52 # Interaction prompt line will separate file and call info from code
148 self.interaction(frame, None)
158 self.interaction(frame, None)
164 Returns True if the normal interaction function must be called,
190 self.interaction(frame, None)
203 self.interaction(frame, exc_traceback)
205 # General interaction function
207 def interaction(self, frame, traceback): member in class:Pdb
[all...] |
| /frameworks/base/packages/SystemUI/src/com/android/systemui/volume/ |
| ZenModePanel.java | 711 // wire up interaction callbacks for newly-added condition rows
713 Interaction.register(tag.rb, mInteractionCallback);
714 Interaction.register(tag.lines, mInteractionCallback);
715 Interaction.register(button1, mInteractionCallback);
716 Interaction.register(button2, mInteractionCallback);
[all...] |
| /external/chromium-trace/catapult/telemetry/docs/pydoc/ |
| telemetry.web_perf.timeline_based_measurement.html | 178 <td colspan=2><tt># TODO(nednguyen): Get rid of this results wrapper hack after we add interaction<br>
207 <td colspan=2><tt>Collects multiple metrics based on their interaction records.<br>
212 issues (via javascript) an Interaction record into the user timing API that<br>
216 interaction records, and a user-chosen amount of performance data using<br>
231 the page_test_results <a href="__builtin__.html#object">object</a> and the interaction record label. This<br>
|
| /frameworks/base/docs/html/guide/topics/ui/ |
| ui-events.jd | 19 <p>On Android, there's more than one way to intercept the events from a user's interaction with your application.
30 called <a href="#EventListeners">event listeners</a>, are your ticket to capturing the user interaction with your UI.</p>
32 <p>While you will more commonly use the event listeners to listen for user interaction, there may
43 been registered is triggered by user interaction with the item in the UI.</p>
202 for interaction named "touch mode."
|
| /device/lge/bullhead/power/ |
| power.c | 72 //interaction boost global variables
235 int interaction(int duration, int num_args, int opt_list[]);
319 // modify downmigrate duration based on interaction data hint
|
| /external/chromium-trace/catapult/telemetry/telemetry/web_perf/metrics/ |
| smoothness.py | 41 Note that if any of the interaction records provided to AddResults have less
199 interaction record in |stats|.
301 'interaction is still bad.',
|
| /frameworks/base/core/java/android/provider/ |
| AlarmClock.java | 49 * This activity could also be started in Voice Interaction mode. The activity should check
90 * Interaction mode (i.e. check {@link android.app.Activity#isVoiceInteraction}), then the
92 * to start a voice interaction follow-on flow to help the user disambiguate the alarm by voice.
|
| /frameworks/base/docs/html/design/wear/ |
| structure.jd | 16 <p>Users are used to tapping icons to launch apps. Android Wear is different. A typical Wear app adds a card to the stream at a contextually relevant moment. It might have a button that opens a full screen view for a fast micro interaction, but it just as well might not.
150 <li>A full screen activity opens for a micro interaction.
155 <p>We highly recommend going full screen only when you can?t do what you want on a card, and quickly exit back to the stream the moment the user is done with the micro interaction. This will make your app will feel like an integrated part of the system. Android Wear itself uses full screen for voice replies and the stopwatch.</p>
|
| /frameworks/base/docs/html/training/design-navigation/ |
| descendant-lateral.jd | 55 <p>Descendant and lateral navigation can be provided using lists, tabs, and other user interface patterns. <em>User interface patterns</em>, much like software design patterns, are generalized, common solutions to recurring interaction design problems. We explore a few common lateral navigation patterns in the sections below.</p>
77 <p>More sophisticated user interfaces can make use of a variety of other user interaction patterns to improve content immediacy and presentation uniqueness, all the while remaining intuitive.</p>
158 <p>In a horizontal paging UI, a single child screen (referred to as a <em>page</em> here) is presented one at a time. Users are able to navigate to sibling screens by touching and dragging the screen horizontally in the direction of the desired adjacent page. This gestural interaction is often complemented by another UI element indicating the current page and available pages, to aid discoverability and provide more context to the user. This practice is especially necessary when using this pattern for lateral navigation of section-related sibling screens. Examples of such elements include tick marks, scrolling labels, and tabs.</p>
|
| /prebuilts/gdb/darwin-x86/lib/python2.7/idlelib/ |
| Debugger.py | 21 self.gui.interaction(message, frame)
28 self.gui.interaction(message, frame, info)
159 def interaction(self, message, frame, info=None): member in class:Debugger
|
| /prebuilts/gdb/linux-x86/lib/python2.7/idlelib/ |
| Debugger.py | 21 self.gui.interaction(message, frame)
28 self.gui.interaction(message, frame, info)
159 def interaction(self, message, frame, info=None): member in class:Debugger
|
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/idlelib/ |
| Debugger.py | 21 self.gui.interaction(message, frame)
28 self.gui.interaction(message, frame, info)
159 def interaction(self, message, frame, info=None): member in class:Debugger
|
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/idlelib/ |
| Debugger.py | 21 self.gui.interaction(message, frame)
28 self.gui.interaction(message, frame, info)
159 def interaction(self, message, frame, info=None): member in class:Debugger
|
| /development/samples/SipDemo/src/com/example/android/sip/ |
| WalkieTalkieActivity.java | 39 * Handles all calling, receiving calls, and UI interaction in the WalkieTalkie app.
194 // Much of the client's interaction with the SIP Stack will
|
| /docs/source.android.com/src/security/authentication/ |
| fingerprint-hal.jd | 109 <img src="../images/fingerprint-daemon.png" alt="Interaction with fingerprintd" id="figure2" />
110 <p class="img-caption"><strong>Figure 2.</strong> Interaction of the
|
