| /frameworks/base/graphics/java/android/graphics/ |
| D | RadialGradient.java | 55 @NonNull int colors[], @Nullable float stops[], @NonNull TileMode tileMode) { in RadialGradient() argument
62 if (stops != null && colors.length != stops.length) { in RadialGradient()
70 mPositions = stops; in RadialGradient()
72 init(nativeCreate1(centerX, centerY, radius, colors, stops, tileMode.nativeInt)); in RadialGradient()
|
| /frameworks/base/core/java/android/text/ |
| D | Layout.java | 1633 int[] stops = this.mStops;
1636 if (stops == null) {
1637 stops = new int[10];
1638 } else if (ns == stops.length) {
1641 nstops[i] = stops[i];
1643 stops = nstops;
1645 stops[ns++] = ((TabStopSpan) o).getTabStop();
1649 Arrays.sort(stops, 0, ns);
1651 if (stops != this.mStops) {
1652 this.mStops = stops;
[all …]
|
| /frameworks/base/docs/html/training/multiple-threads/ |
| D | run-code.jd | 130 In most cases, {@link java.lang.Thread#interrupt Thread.interrupt()} stops the thread
131 immediately. However, it only stops threads that are waiting, and will not interrupt CPU or
|
| /frameworks/base/docs/html/training/run-background-service/ |
| D | send-request.jd | 76 {@link android.app.IntentService#onHandleIntent onHandleIntent()} method, and then stops itself.
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| D | instrumentation-element.jd | 33 stops, and "{@code false}" if profiling continues the entire time it is
|
| /frameworks/base/docs/html/tools/debugging/ |
| D | debugging-tracing.jd | 101 DDMS. Although you have less control on exactly where logging starts and stops,
152 stopMethodTracing()}, the system stops tracing
282 <li>The VM reuses thread IDs. If a thread stops and another starts, they may get the same
|
| D | ddms.jd | 209 <li>Click the <strong>Stop Method Profiling</strong> button. DDMS stops profiling your
|
| /frameworks/native/opengl/libs/GLES_trace/ |
| D | DESIGN.txt | 26 Currently, the application is killed when the user stops tracing from the frontend GUI. We need
|
| /frameworks/base/docs/html/design/patterns/ |
| D | gestures.jd | 40 and the screen stops responding when the finger is picked up.</p>
|
| D | notifications_k.jd | 346 the notification system and continue to do so until the user stops the
|
| /frameworks/base/services/core/java/com/android/server/am/ |
| D | ActivityStackSupervisor.java | 2272 ArrayList<ActivityRecord> stops = null; in activityIdleInternalLocked() local
2326 stops = processStoppingActivitiesLocked(true); in activityIdleInternalLocked()
2327 NS = stops != null ? stops.size() : 0; in activityIdleInternalLocked()
2341 r = stops.get(i); in activityIdleInternalLocked()
3075 ArrayList<ActivityRecord> stops = null; in processStoppingActivitiesLocked()
3098 if (stops == null) { in processStoppingActivitiesLocked()
3099 stops = new ArrayList<ActivityRecord>(); in processStoppingActivitiesLocked()
3101 stops.add(s); in processStoppingActivitiesLocked()
3108 return stops; in processStoppingActivitiesLocked()
|
| /frameworks/base/docs/html/training/location/ |
| D | location-testing.jd | 224 stops itself. This also stops the background thread.
279 to turn off mock mode and then stop itself. When the service stops itself, the background
|
| D | display-address.jd | 110 stops itself when it runs out of work. The intent extras provide the data
|
| D | geofencing.jd | 766 isn't called, and the request stops.
1101 and the request stops. The following snippet shows how to start the request:
|
| /frameworks/base/docs/html/guide/components/ |
| D | services.jd | 158 remains running until it stops itself with {@link android.app.Service#stopSelf()} or another
159 component stops it by calling {@link android.content.Context#stopService stopService()}.</p>
233 attribute and setting it to {@code "false"}. This effectively stops other apps from starting your
261 database transaction. When the transaction is done, the service stops itself and it is
333 * stops the service, as appropriate.
566 <p class="caution"><strong>Caution:</strong> It's important that your application stops its services
|
| D | tasks-and-back-stack.jd | 90 stops, the system retains the current state of its user interface. When the user presses the
195 <p>When the system stops one of your activities (such as when a new activity starts or the task
|
| /frameworks/base/docs/html/training/basics/activity-lifecycle/ |
| D | pausing.jd | 40 <p>However, once the activity is fully-obstructed and not visible, it <em>stops</em> (which is
|
| /frameworks/base/docs/html/training/managing-audio/ |
| D | audio-focus.jd | 139 unregisters our media button event receiver and stops monitoring audio focus changes.<p>
|
| /frameworks/base/docs/html/training/wearables/apps/ |
| D | layouts.jd | 139 and automatically snaps to the nearest item when the user stops scrolling.
|
| /frameworks/base/docs/html/tools/testing/ |
| D | service_testing.jd | 169 will stop the Service. You should test that your Service stops at the correct point.
|
| /frameworks/base/docs/html/tools/help/ |
| D | monkey.jd | 218 <td>Normally, when the Monkey stops due to an error, the application that failed will be left
|
| /frameworks/base/docs/html/training/gestures/ |
| D | scroll.jd | 102 want to keep scrolling (moving the viewport), but decelerate until the viewport stops moving.
|
| /frameworks/base/docs/html/training/wearables/watch-faces/ |
| D | drawing.jd | 259 mode. When the watch face is not visible, this method stops the custom timer and unregisters
|
| /frameworks/base/docs/html/training/game-controllers/ |
| D | compatibility.jd | 394 disconnected. The {@link android.os.Handler} stops polling when the app is
|
| /frameworks/base/docs/html/training/basics/network-ops/ |
| D | xml.jd | 337 <li>To make sure that it stops at the correct <code>END_TAG</code> and not at
|