Home
last modified time | relevance | path

Searched refs:ranges (Results 1 – 13 of 13) sorted by relevance

/frameworks/rs/scriptc/
Drs_time.rsh36 * tm_sec - Seconds after the minute. This ranges from 0 to 59, but possibly
38 * tm_min - Minutes after the hour. This ranges from 0 to 59.
39 * tm_hour - Hours past midnight. This ranges from 0 to 23.
40 * tm_mday - Day of the month. This ranges from 1 to 31.
41 * tm_mon - Months since January. This ranges from 0 to 11.
43 * tm_wday - Days since Sunday. This ranges from 0 to 6.
44 * tm_yday - Days since January 1. This ranges from 0 to 365.
/frameworks/base/core/jni/
Dandroid_view_InputDevice.cpp62 const Vector<InputDeviceInfo::MotionRange>& ranges = deviceInfo.getMotionRanges(); in android_view_InputDevice_create() local
63 for (size_t i = 0; i < ranges.size(); i++) { in android_view_InputDevice_create()
64 const InputDeviceInfo::MotionRange& range = ranges.itemAt(i); in android_view_InputDevice_create()
/frameworks/native/opengl/libagl/
DTokenizer.cpp164 const run_t* ranges = mRanges.array(); in dump() local
168 ALOGD("%u: (%u, %u)\n", i, ranges[i].first, ranges[i].length); in dump()
/frameworks/base/docs/html/about/
Dmarketplace.jd60 markets and devices or focus on specific segments, devices, or ranges of hardware capabilities.
Dindex.jd103 devices or focus on specific segments, devices, or ranges of hardware
/frameworks/base/docs/html/about/versions/
Dandroid-3.2.jd95 target specific screen ranges by their dimensions, measured in
192 for ranges of screen sizes. Using the qualifiers, you can create resource
Dandroid-3.1-highlights.jd334 ranges (axes) supported by each device. Applications can also handle multiple
Dandroid-4.0.jd1787 ability to precisely target specific screen size ranges by dimensions, measured in
/frameworks/base/docs/html/distribute/googleplay/publish/
Dpreparing.jd12 <li><a href="#compatibility">6. Confirm app compatibility ranges</a></li>
183 <h2 id="compatibility">6. Confirm the app's platform and screen compatibility ranges</h2>
/frameworks/base/services/input/
DInputReader.cpp887 const Vector<InputDeviceInfo::MotionRange>& ranges = deviceInfo.getMotionRanges(); in dump() local
888 if (!ranges.isEmpty()) { in dump()
890 for (size_t i = 0; i < ranges.size(); i++) { in dump()
891 const InputDeviceInfo::MotionRange& range = ranges.itemAt(i); in dump()
/frameworks/base/docs/html/tools/devices/
Demulator.jd886 built-in limitations on port numbers or ranges except the one imposed by your
/frameworks/base/docs/html/guide/practices/
Dscreens_support.jd190 <img src="{@docRoot}images/screens_support/screens-ranges.png" style="padding:1em 0 0" alt="" />
/frameworks/base/tests/DumpRenderTree/assets/results/
Dlayout_tests_passed.txt1704 /sdcard/android/layout_tests/fast/js/regexp-ranges-and-escaped-hyphens.html