/frameworks/base/docs/html/design/patterns/ |
app-structure.jd | 107 <p><em>Fixed tabs</em> display top-level views concurrently and make it easy to explore and switch between them. They are always visible on the screen, and can't be moved out of the way like scrollable tabs. <em>Fixed tabs</em> should always allow the user to navigate between the views by swiping left or right on the content area.</p>
|
/frameworks/base/docs/html/distribute/googleplay/about/ |
visibility.jd | 43 with a browser can explore everything that Google Play has to offer from its <a
|
/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>
|
/frameworks/base/services/java/com/android/server/accessibility/ |
TouchExplorer.java | 146 // Helper to detect and react to double tap in touch explore mode. [all...] |
/frameworks/support/v4/java/android/support/v4/accessibilityservice/ |
AccessibilityServiceInfoCompat.java | 227 * shown to the user to confirm enabling explore by touch.
|
/packages/apps/Launcher3/src/com/android/launcher3/ |
LauncherClings.java | 88 // Disable clings for accessibility when explore by touch is enabled
|
/sdk/find_java/ |
find_java_lib.cpp | 195 // Explore the registry to find a suitable version of Java.
|
/external/clang/lib/StaticAnalyzer/Core/ |
ExprEngineCallAndReturn.cpp | 401 // the exact type of the receiver is not known, we want to explore both paths - [all...] |
/external/openfst/src/test/ |
algo_test.h | 846 // Number of random paths to explore. [all...] |
/frameworks/base/core/res/res/values-be/ |
strings.xml | 244 <string name="capability_title_canRequestTouchExploration" msgid="3108723364676667320">"???????? Explore by Touch"</string> [all...] |
/frameworks/base/docs/html/guide/topics/ui/accessibility/ |
apps.jd | 76 <a href="{@docRoot}tools/testing/testing_accessibility.html#testing-ebt">Explore by Touch</a>, 410 <p class="note"><strong>Note:</strong> Hover events are associated with the Explore by [all...] |
/external/chromium/chrome/browser/resources/net_internals/ |
index.html | 189 <a href="chrome://view-http-cache" target=_blank>Explore cache entries</a>
|
/external/chromium/chrome/common/extensions/docs/ |
devguide.html | 374 <td> Explore and modify the browser's cookie system </td>
|
tut_debugging.html | 576 explore the
|
/external/chromium_org/chrome/test/perf/ |
memory_test.cc | 346 "http://flickr.com/explore/interesting/2008/03/18/",
|
/external/chromium_org/third_party/libwebp/enc/ |
filter.c | 359 // explore +/-quant range of values around level0
|
/external/libvorbis/doc/ |
stereo.html | 102 explore below, and using both we can implement both totally
|
/external/libvorbis/vq/ |
vqgen.c | 23 /* There are so many optimizations to explore in *both* stages that
|
/external/qemu/android/utils/ |
timezone.c | 708 /* we didn't find it, this may come from localized versions of Windows. we're going to explore the registry,
|
/external/qemu/distrib/sdl-1.2.15/docs/html/ |
guideinputkeyboard.html | 351 >This is a very basic example. No information about the key press or release is interpreted. We will explore the other extreme out our first full example below - reporting all available information about a keyboard event.</P
|
/external/webp/src/enc/ |
filter.c | 359 // explore +/-quant range of values around level0
|
/frameworks/base/core/java/android/accessibilityservice/ |
AccessibilityServiceInfo.java | 231 * shown to the user to confirm enabling explore by touch. [all...] |
/frameworks/base/core/java/android/provider/ |
DocumentsProvider.java | 249 * issued to recursively explore the tree.
|
/frameworks/base/docs/html/distribute/googleplay/spotlight/ |
tablets.jd | 342 Mobelux. ?It was a market that others were hesitant to explore, but the decision
|
/frameworks/support/v4/java/android/support/v4/widget/ |
ExploreByTouchHelper.java | 115 * the Explore by Touch feature is enabled.
|