HomeSort by relevance Sort by last modified time
    Searched full:interactions (Results 126 - 150 of 372) sorted by null

1 2 3 4 56 7 8 91011>>

  /frameworks/base/docs/html/preview/
api-overview.jd 27 <li><a href="#voice-interactions">Voice Interactions</a></li>
229 <h2 id="voice-interactions">Voice Interactions</h2>
239 <p>Most voice interactions originate from a user voice action. A voice interaction activity can
308 interactions:</p>
    [all...]
  /packages/apps/Contacts/src/com/android/contacts/activities/
PeopleActivity.java 62 import com.android.contacts.interactions.ContactDeletionInteraction;
63 import com.android.contacts.common.interactions.ImportExportDialogFragment;
68 import com.android.contacts.interactions.ContactMultiDeletionInteraction;
69 import com.android.contacts.interactions.ContactMultiDeletionInteraction.MultiContactDeleteListener;
70 import com.android.contacts.interactions.JoinContactsDialogFragment;
71 import com.android.contacts.interactions.JoinContactsDialogFragment.JoinContactsListener;
    [all...]
  /frameworks/base/core/java/android/nfc/
Tag.java 65 * This is important for NFC interactions because they are very transient -- if a user has to
107 * contain operating environments allowing complex interactions with the
  /frameworks/base/docs/html/design/wear/
patterns.jd 6 <p>Android Wear is used for micro-interactions, and so adhering to consistent design patterns that users are already accustomed to is paramount.</p>
135 <p>In some instances, further information may be required. In these cases, the most probable default values for these choices should be chosen on the user?s behalf with the option to edit before completing the action. This pattern is in keeping with Android Wear?s core design principle of minimizing interactions required.</p>
  /frameworks/base/docs/html/guide/practices/app-design/
seamlessness.jd 25 still cause problems for users &mdash; because of unplanned interactions with
28 your applications run and the system interactions that can affect your
  /frameworks/base/docs/html/guide/practices/
seamlessness.jd 26 still cause problems for users &mdash; because of unplanned interactions with
29 your applications run and the system interactions that can affect your
  /frameworks/base/docs/html/guide/topics/ui/accessibility/
checklist.jd 159 <li><strong>Custom controls with complex visual interactions:</strong> For custom controls that
160 provide complex or non-standard visual interactions, provide a
  /frameworks/base/docs/html/training/design-navigation/
descendant-lateral.jd 100 <p>Using vertical lists can also lead to awkward user interactions and poor use of whitespace on larger screens, as list items generally span the entire width of the screen yet have a fixed height. One way to alleviate this is to provide additional information, such as text summaries, that fills the available horizontal space. Another way is to provide additional information in a separate horizontal pane adjacent to the list.</p>
167 <p>It's also best to avoid this pattern when child screens contain horizontal panning surfaces (such as maps), as these conflicting interactions may deter your screen's usability.</p>
  /frameworks/base/docs/html-intl/intl/ja/preview/
api-overview.jd 27 <li><a href="#voice-interactions">??????????</a></li>
211 <h2 id="voice-interactions">??????????</h2>
  /frameworks/base/docs/html-intl/intl/ko/preview/
api-overview.jd 27 <li><a href="#voice-interactions">?? ????</a></li>
211 <h2 id="voice-interactions">?? ????</h2>
  /frameworks/base/docs/html-intl/intl/ru/preview/
api-overview.jd 27 <li><a href="#voice-interactions">????????? ?????????</a></li>
211 <h2 id="voice-interactions">????????? ?????????</h2>
    [all...]
  /frameworks/base/docs/html-intl/intl/zh-cn/preview/
api-overview.jd 27 <li><a href="#voice-interactions">????</a></li>
211 <h2 id="voice-interactions">????</h2>
  /frameworks/base/docs/html-intl/intl/zh-tw/preview/
api-overview.jd 27 <li><a href="#voice-interactions">????</a></li>
211 <h2 id="voice-interactions">????</h2>
  /frameworks/native/include/gui/
IGraphicBufferConsumer.h 152 // interactions with the BufferQueue by the producer to fail.
165 // state, causing most interactions with the BufferQueue by the producer to
  /packages/apps/Dialer/src/com/android/dialer/interactions/
PhoneNumberInteraction.java 16 package com.android.dialer.interactions;
65 * dialog to pick one. Creating one of these interactions should be done through the static
  /cts/tests/tests/os/src/android/os/cts/
ParcelFileDescriptorProcessTest.java 39 * Test various cross-process {@link ParcelFileDescriptor} interactions.
  /developers/build/prebuilts/gradle/NavigationDrawer/Application/src/main/java/com/example/android/navigationdrawer/
NavigationDrawerActivity.java 100 // ActionBarDrawerToggle ties together the the proper interactions
  /developers/samples/android/ui/views/NavigationDrawer/Application/src/main/java/com/example/android/navigationdrawer/
NavigationDrawerActivity.java 100 // ActionBarDrawerToggle ties together the the proper interactions
  /development/samples/Support4Demos/src/com/example/android/supportv4/widget/
DrawerLayoutActivity.java 105 // prescribed interactions between a top-level sliding drawer and the action bar.
  /development/samples/browseable/NavigationDrawer/src/com.example.android.navigationdrawer/
NavigationDrawerActivity.java 100 // ActionBarDrawerToggle ties together the the proper interactions
  /development/samples/training/NavigationDrawer/src/com/example/android/navigationdrawerexample/
MainActivity.java 100 // ActionBarDrawerToggle ties together the the proper interactions
  /external/chromium-trace/trace-viewer/tracing/tracing/ui/extras/rail/
rail_score_side_panel.html 110 reason: 'RAIL interactions were not found on the model'
  /external/ksoap2/ksoap2-base/src/main/java/org/ksoap2/transport/
Transport.java 43 * Added to enable web service interactions on the emulator
  /external/valgrind/coregrind/m_syswrap/
syscall-arm-linux.S 48 interactions.
syscall-arm64-linux.S 49 interactions.

Completed in 386 milliseconds

1 2 3 4 56 7 8 91011>>