| /frameworks/base/location/java/android/location/ |
| D | Location.java | 193 public static String convert(double coordinate, int outputType) { in convert() argument
194 if (coordinate < -180.0 || coordinate > 180.0 || in convert()
195 Double.isNaN(coordinate)) { in convert()
196 throw new IllegalArgumentException("coordinate=" + coordinate); in convert()
207 if (coordinate < 0) { in convert()
209 coordinate = -coordinate; in convert()
214 int degrees = (int) Math.floor(coordinate); in convert()
217 coordinate -= degrees; in convert()
218 coordinate *= 60.0; in convert()
220 int minutes = (int) Math.floor(coordinate); in convert()
[all …]
|
| /frameworks/base/docs/html/training/graphics/opengl/ |
| D | shapes.jd | 40 <p>This lesson explains the OpenGL ES coordinate system relative to an Android device screen, the
71 // (number of coordinate values * 4 bytes per float)
80 // set the buffer to read the first coordinate
86 <p>By default, OpenGL ES assumes a coordinate system where [0,0,0] (X,Y,Z) specifies the center of
88 [-1,-1,0] is bottom left corner of the frame. For an illustration of this coordinate system, see the
89 <a href="{@docRoot}guide/topics/graphics/opengl.html#coordinate-mapping">OpenGL ES</a> developer
133 // (# of coordinate values * 4 bytes per float)
142 // (# of coordinate values * 2 bytes per short)
|
| D | projection.jd | 49 coordinate mapping, see <a
50 href="{@docRoot}guide/topics/graphics/opengl.html#coordinate-mapping">Mapping Coordinates for Drawn
|
| D | draw.jd | 193 // Prepare the triangle coordinate data
|
| /frameworks/support/core-ui/java/android/support/v4/widget/ |
| D | AutoScrollHelper.java | 538 int direction, float coordinate, float srcSize, float dstSize) { in computeTargetVelocity() argument
541 final float value = getEdgeValue(relativeEdge, srcSize, maximumEdge, coordinate); in computeTargetVelocity()
|
| /frameworks/base/core/java/com/android/internal/widget/ |
| D | AutoScrollHelper.java | 537 int direction, float coordinate, float srcSize, float dstSize) { in computeTargetVelocity() argument
540 final float value = getEdgeValue(relativeEdge, srcSize, maximumEdge, coordinate); in computeTargetVelocity()
|
| /frameworks/base/packages/DocumentsUI/src/com/android/documentsui/dirlist/ |
| D | MultiSelectManager.java | 2007 private int getCoordinateValue(RelativeCoordinate coordinate, in getCoordinateValue() argument
2009 switch (coordinate.type) { in getCoordinateValue()
2016 return coordinate.limitsAfterCoordinate.lowerLimit; in getCoordinateValue()
2018 return coordinate.limitsBeforeCoordinate.upperLimit; in getCoordinateValue()
2021 return coordinate.limitsBeforeCoordinate.lowerLimit; in getCoordinateValue()
|
| /frameworks/base/docs/html/guide/topics/sensors/ |
| D | sensors_motion.jd | 71 acceleration force data for the three coordinate axes, and the gyroscope returns rate of rotation
72 data for the three coordinate axes. These data values are returned in a <code>float</code> array
295 href="{@docRoot}guide/topics/sensors/sensors_overview.html#sensors-coords">coordinate
334 sensor (m/s<sup>2</sup>), and the coordinate system is the same as the one used by the
353 href="{@docRoot}guide/topics/sensors/sensors_overview.html#sensors-coords">coordinate system</a>
478 href="{@docRoot}guide/topics/sensors/sensors_overview.html#sensors-coords">coordinate
517 coordinate system is defined as a direct orthonormal basis (see figure 1). This coordinate system
|
| D | sensors_position.jd | 79 each of the three coordinate axes during a single sensor event. Likewise, the
81 sensor event. For more information about the coordinate systems that are used
306 Note that these angles work off of a different coordinate system than the
411 coordinate system to your application's frame of reference.
427 <p>This sensor provides raw field strength data (in μT) for each of the three coordinate axes.
|
| D | sensors_overview.jd | 694 <p>In general, the sensor framework uses a standard 3-axis coordinate system to express data values.
695 For most sensors, the coordinate system is defined relative to the device's screen when the device
699 have negative Z values. This coordinate system is used by the following sensors:</p>
726 <p>The most important point to understand about this coordinate system is that the axes are not
727 swapped when the device's screen orientation changes—that is, the sensor's coordinate system
729 coordinate system.</p>
733 the sensor coordinate system is always based on the natural orientation of a device.</p>
741 <p>For more information about the sensor coordinate system, including information about how to
746 <p class="note"><strong>Note:</strong> Some sensors and methods use a coordinate system that is
|
| /frameworks/rs/java/tests/Refocus/src/com/android/rs/test/ |
| D | layered_filter_f32_helper.rsh | 12 // @param x x-coordinate of a pixel in a padded image.
13 // @param y y-coordinate of a pixel in a padded image.
|
| D | luts_for_speedup_f32.rsh | 62 // A lookup table that pre-computes x coordinate of the intersection between a
|
| D | layered_filter_d1new_helper.rsh | 29 // @param x x-coordinate of a pixel in a padded image.
30 // @param y y-coordinate of a pixel in a padded image.
|
| /frameworks/base/cmds/bootanimation/ |
| D | FORMAT.md | 42 * **CLOCK:** _(OPTIONAL)_ the y-coordinate at which to draw the current time (for watches)
|
| /frameworks/base/docs/html/guide/topics/graphics/ |
| D | opengl.jd | 15 <li><a href="#coordinate-mapping">Mapping Coordinates for Drawn Objects</a>
258 <h2 id="coordinate-mapping">Mapping Coordinates for Drawn Objects</h2>
261 vary in size and shape. OpenGL assumes a square, uniform coordinate system and, by default, happily
266 <strong>Figure 1.</strong> Default OpenGL coordinate system (left) mapped to a typical Android
270 <p>The illustration above shows the uniform coordinate system assumed for an OpenGL frame on the
307 <li><strong>Camera transformation matrix</strong> - Once you have adjusted the coordinate system
445 <strong>Figure 1.</strong> Illustration of a coordinate list which translates into a
|
| /frameworks/base/packages/WallpaperCropper/src/com/android/gallery3d/exif/ |
| D | ExifInterface.java | 1909 public static double convertLatOrLongToDouble(Rational[] coordinate, String reference) { in convertLatOrLongToDouble() argument
1911 double degrees = coordinate[0].toDouble(); in convertLatOrLongToDouble()
1912 double minutes = coordinate[1].toDouble(); in convertLatOrLongToDouble()
1913 double seconds = coordinate[2].toDouble(); in convertLatOrLongToDouble()
|
| /frameworks/base/docs/html/topic/performance/power/network/ |
| D | action-app-traffic.jd | 23 these functions can coordinate network access for other apps, further optimizing battery
|
| /frameworks/base/docs/html/guide/topics/renderscript/ |
| D | compute.jd | 93 once for every coordinate in those dimensions. It is typically (but not exclusively) used to
147 coordinate in those dimensions. It is typically (but not exclusively) used to "reduce" a
422 kernel executes over every coordinate in those dimensions; to execute a kernel over a subset of tho…
578 <li>searching for a specific value or for the coordinate of a specific value within the data</li>
737 <p>RenderScript calls your accumulator function once for every coordinate in the
752 <p>After the accumulator function has been called once for every coordinate in the input(s),
835 this function once for every coordinate in the input(s), to update an
857 once for every coordinate in the input(s), it calls this function as many
1112 value <i>V</i> at coordinate <i>X</i>:
1188 kernel executes over every coordinate in those dimensions.</p>
|
| /frameworks/base/docs/html/guide/topics/resources/ |
| D | animation-resource.jd | 464 <dd><em>Float</em>. The X coordinate to remain fixed when the object is scaled.</dd>
466 <dd><em>Float</em>. The Y coordinate to remain fixed when the object is scaled.</dd>
510 <dd><em>Float or percentage</em>. The X coordinate of the center of rotation. Expressed
515 <dd><em>Float or percentage</em>. The Y coordinate of the center of rotation. Expressed
|
| /frameworks/base/docs/html/guide/topics/ui/ |
| D | declaring-layout.jd | 239 coordinate of the rectangle representing the view. The latter returns the
240 top, or Y, coordinate of the rectangle representing the view. These methods
|
| D | drag-drop.jd | 818 return the X and Y position of the drag point at the moment of the drop, using the coordinate
|
| /frameworks/base/docs/html/training/game-controllers/ |
| D | controller-input.jd | 113 coordinate of the touch surface, but a joystick generates an {@link android.view.MotionEvent#AXIS_X…
543 have a <em>flat</em> area, that is, a range of values near the (0,0) coordinate
|
| /frameworks/base/docs/html/training/printing/ |
| D | custom-docs.jd | 354 of elements on the page. For positioning of drawn elements, the coordinate system starts at 0,0
|
| /frameworks/base/docs/html/guide/topics/media/ |
| D | camera.jd | 1175 <strong>Figure 1.</strong> The red lines illustrate the coordinate system for specifying a
1180 <p>The bounds of this coordinate system always correspond to the outer edge of the image visible in
1183 does not remap the coordinate system.</p>
|
| /frameworks/base/docs/html/guide/components/ |
| D | bound-services.jd | 629 activities coordinate their lifecycles is described in the <a
|