| /external/libgdx/extensions/gdx-box2d/gdx-box2d-gwt/src/com/badlogic/gdx/physics/box2d/gwt/emu/com/badlogic/gdx/physics/box2d/ |
| World.java | 210 * you will disable auto clearing of forces and instead call ClearForces after all sub-steps are complete in one pass of your
261 /** Set flag to control automatic clearing of forces after each time step. */
266 /** Get the flag that controls automatic clearing of forces after each time step. */
|
| /external/mesa3d/src/mesa/drivers/dri/intel/ |
| intel_blit.c | 224 * which we're clearing with triangles.
238 * Compute values for clearing the buffers.
309 /* clearing RGBA */
|
| /external/v8/test/cctest/ |
| test-feedback-vector.cc | 163 // We only test clearing FeedbackVectorSlots, not FeedbackVectorSlots.
180 // GC time clearing leaves slots alone.
188 // an exemption from clearing, as are smis.
|
| /external/v8/tools/turbolizer/ |
| graph-layout.js | 404 console.log("After clearing outputs");
441 console.log("Before clearing nodes");
448 console.log("After clearing nodes");
|
| /external/wpa_supplicant_8/src/utils/ |
| eloop.h | 86 * socket. The handler function is responsible for clearing the event after
113 * socket. The handler function is responsible for clearing the event after
145 * function is responsible for clearing the event after having processed it in
|
| /frameworks/base/docs/html-intl/intl/ja/guide/components/ |
| tasks-and-back-stack.jd | 16 <li><a href="#Clearing">?????????????</a></li>
487 <h3 id="Clearing">?????????????</h3>
560 <p>??????????????????????<code><a href="{@docRoot}guide/topics/manifest/activity-element.html"><activity></a></code> ?????? <a href="{@docRoot}guide/topics/manifest/activity-element.html#finish">{@code finishOnTaskLaunch}</a> ? {@code "true"} ???????<a href="#Clearing">??????????</a>?????????
|
| /frameworks/base/docs/html-intl/intl/ko/guide/components/ |
| tasks-and-back-stack.jd | 16 <li><a href="#Clearing">? ?? ???</a></li>
487 <h3 id="Clearing">? ?? ???</h3>
564 ? {@code "true"}? ???? ???(<a href="#Clearing">?? ???</a>? ??????).</p>
|
| /frameworks/base/docs/html-intl/intl/ru/guide/components/ |
| tasks-and-back-stack.jd | 16 <li><a href="#Clearing">??????? ????? ????????? ?????</a></li>
487 <h3 id="Clearing">??????? ????? ????????? ?????</h3>
[all...] |
| /frameworks/base/docs/html-intl/intl/zh-cn/guide/components/ |
| tasks-and-back-stack.jd | 16 <li><a href="#Clearing">?????</a></li>
487 <h3 id="Clearing">?????</h3>
564 ??? {@code "true"}????<a href="#Clearing">????</a>??</p>
|
| /frameworks/base/docs/html-intl/intl/zh-tw/guide/components/ |
| tasks-and-back-stack.jd | 16 <li><a href="#Clearing">??????</a></li>
487 <h3 id="Clearing">??????</h3>
562 <a href="{@docRoot}guide/topics/manifest/activity-element.html#finish">{@code finishOnTaskLaunch}</a> ??? {@code "true"} (???<a href="#Clearing">????</a>)?
|
| /frameworks/base/core/java/android/app/ |
| UiAutomation.java | 788 Log.i(LOG_TAG, "Clearing content frame stats for window: " + windowId);
793 Log.e(LOG_TAG, "Error clearing window content frame stats!", re);
802 * A typical usage requires clearing the window frame statistics via {@link
858 Log.i(LOG_TAG, "Clearing window animation frame stats");
863 Log.e(LOG_TAG, "Error clearing window animation frame stats!", re);
[all...] |
| /cts/tests/tests/calllog/src/android/calllog/cts/ |
| CallLogBackupTest.java | 147 Log.i(TAG, "Clearing the call log");
161 Log.i(TAG, "Clearing the call log");
|
| /external/guava/guava-testlib/src/com/google/common/testing/ |
| GcFinalization.java | 38 * <li>clearing weak references to unreachable referents
204 * <li>clearing weak references to unreachable referents
|
| /external/mesa3d/src/gallium/auxiliary/util/ |
| u_surface.c | 228 * Plus can't use these transfer fallbacks when clearing
273 * Plus can't use these transfer fallbacks when clearing
|
| /external/opencv/cv/src/ |
| cvcalccontrasthistogram.cpp | 58 // Notes: if dont_clear parameter is NULL then histogram clearing before
171 // Notes: if dont_clear parameter is NULL then histogram clearing before
|
| /external/opencv3/3rdparty/jinja2/ |
| bccache.py | 200 This bytecode cache supports clearing of the cache using the clear method.
278 This bytecode cache does not support clearing of used items in the cache.
|
| /external/v8/src/base/ |
| hashmap.h | 166 // initial position inside this interval, clearing the entry to remove will
200 // found. There is now a new candidate entry for clearing.
|
| /external/v8/src/regexp/arm64/ |
| regexp-macro-assembler-arm64.h | 194 // Register holding the value used for clearing capture registers.
197 // twice. This is used for clearing more than one register at a time.
|
| /external/vboot_reference/firmware/2lib/ |
| 2misc.c | 155 * Note that we ignore failures clearing the request. We only
298 /* Try clearing */
|
| /frameworks/base/docs/html/guide/topics/search/ |
| adding-recent-query-suggestions.jd | 15 <li><a href="#ClearingSuggestionData">Clearing the Suggestion Data</a></li>
221 <h2 id="ClearingSuggestionData">Clearing the Suggestion Data</h2>
|
| /frameworks/base/docs/html/topic/performance/power/network/ |
| gather-data.jd | 210 your app by clearing app data. The following procedure includes a step that shows you how to
251 <li>Repeat the test by clearing the app data and running your test plan again. You should repeat
|
| /frameworks/native/libs/binder/ |
| BpBinder.cpp | 229 ALOGV("Clearing death notification: %p handle %d\n", this, mHandle);
254 ALOGV("Clearing sent death notification: %p handle %d\n", this, mHandle);
|
| /bionic/libc/upstream-openbsd/lib/libc/stdio/ |
| open_wmemstream.c | 102 * XXX Clearing mbs here invalidates shift state for state-
|
| /cts/hostsidetests/appsecurity/test-apps/DocumentClient/src/com/android/cts/documentclient/ |
| DocumentsClientTestCase.java | 159 Log.d(TAG, "Not clearing DocumentsUI due to test name: " + testName);
|
| /cts/hostsidetests/appsecurity/test-apps/UsePermissionDiffCert/src/com/android/cts/usespermissiondiffcertapp/ |
| ModifyInstallerPackageTest.java | 208 receiver.assertSuccess("Failure clearing other installer");
|
