HomeSort by relevance Sort by last modified time
    Searched full:interactions (Results 51 - 75 of 338) sorted by null

1 23 4 5 6 7 8 91011>>

  /external/chromium/net/base/
cookie_monster_store_test.h 7 // that need to test out CookieMonster interactions with the backing store.
  /external/chromium_org/apps/app_shim/
app_shim_handler_mac.h 18 // Registrar, and interface for services that can handle interactions with OSX
  /external/chromium_org/chrome/browser/lifetime/
application_lifetime.h 64 // interactions, so it will always exit the browser. This is used to
  /external/chromium_org/chrome/browser/password_manager/
password_store_mac.h 25 // database for extra metadata. For an overview of the interactions with the
  /external/chromium_org/chrome/browser/prefs/
proxy_config_dictionary.cc 14 // See ProxyPrefs for possible values and interactions with the other proxy
  /external/chromium_org/chrome/browser/ui/cocoa/
profile_signin_confirmation_view_controller_browsertest.mm 77 // Visible for testing UI interactions.
  /external/chromium_org/content/browser/web_contents/
web_contents_view_win.h 133 // The helper object that handles drag destination related interactions with
  /external/chromium_org/ppapi/native_client/tests/ppapi_test_lib/
module_instance.cc 6 // instance in browser interactions and provides a way to register custom
  /external/chromium_org/third_party/skia/include/core/
SkImage.h 69 * interactions with scratch cache still has issues, so for now we take
  /external/mockito/src/org/mockito/verification/
VerificationWithTimeout.java 49 * If you want to verify there were NO interactions with the mock
  /external/skia/include/core/
SkImage.h 69 * interactions with scratch cache still has issues, so for now we take
  /frameworks/base/docs/html/guide/topics/connectivity/nfc/
index.jd 12 contain operating environments, allowing complex interactions with code executing on the tag.
  /frameworks/base/docs/html/training/basics/intents/
index.jd 49 interactions with other apps, such as start another app, receive a result from that app, and
  /frameworks/base/docs/html/training/design-navigation/
index.jd 22 <p>One of the very first steps to designing and developing an Android application is to determine what users are able to see and do with the app. Once you know what kinds of data users are interacting with in the app, the next step is to design the interactions that allow users to navigate across, into, and back out from the different pieces of content within the app.</p>
  /frameworks/base/docs/html/training/in-app-billing/
index.jd 29 <p>In-app billing is a service hosted on Google Play that lets you charge for digital content or for upgrades in your app. The In-app Billing API makes it easy for you to integrate In-app Billing into your applications. You can request product details from Google Play, issue orders for in-app products, and quickly retrieve ownership information based on users' purchase history. You can also query the Google Play service for details about in-app products, such as local pricing and availability. Google Play provides a checkout interface that makes user interactions with the In-app Billing service seamless, and provides a more intuitive experience to your users.</p>
  /external/ceres-solver/internal/ceres/
visibility_based_preconditioner.h 77 // cameras that we expect have strong interactions, and then using the
97 // identifying strong interactions between cluster pairs. This is done
  /docs/source.android.com/src/devices/
audio_avoiding_pi.jd 171 Note: atomic operations and their interactions with memory barriers
292 system and the interactions. Tools such as
  /external/chromium_org/chrome/browser/ui/views/
chrome_views_delegate.cc 227 // interactions. On Windows however these WM interactions are not an issue, so
  /external/mockito/src/org/mockito/
MockSettings.java 126 * Specifies default answers to interactions.
166 * during test debugging in order to find wrong interactions with this mock.
  /frameworks/base/docs/html/tools/testing/
contentprovider_testing.jd 126 database operations but stubs out other interactions with the Android system.
192 Test the standard provider interactions: Most providers offer six access methods:
  /frameworks/native/include/gui/
IGraphicBufferConsumer.h 135 // interactions with the BufferQueue by the producer to fail.
144 // state, causing most interactions with the BufferQueue by the producer to
  /packages/apps/Contacts/src/com/android/contacts/editor/
GroupMembershipView.java 41 import com.android.contacts.interactions.GroupCreationDialogFragment;
42 import com.android.contacts.interactions.GroupCreationDialogFragment.OnGroupCreatedListener;
  /art/test/ThreadStress/
ThreadStress.java 62 // interactions between the threads.
  /development/samples/ApiDemos/src/com/example/android/apis/app/
NotifyingService.java 117 // This is the object that receives interactions from clients. See
  /external/chromium/chrome/browser/
keychain_mock_mac.h 110 // user interactions.

Completed in 435 milliseconds

1 23 4 5 6 7 8 91011>>