Home
last modified time | relevance | path

Searched refs:destroyed (Results 1 – 25 of 29) sorted by relevance

12

/frameworks/base/libs/hwui/
DResourceCache.cpp35 i, ref->refCount, ref->recycled, ref->destroyed, ref->resourceType); in logCache()
141 ref->destroyed = true; in destructor()
158 ref->destroyed = true; in destructor()
172 ref->destroyed = true; in destructor()
186 ref->destroyed = true; in destructor()
200 if (ref->destroyed) { in deleteResourceReference()
DResourceCache.h43 ResourceReference() { refCount = 0; recycled = false; destroyed = false;} in ResourceReference()
45 refCount = 0; recycled = false; destroyed = false; resourceType = type; in ResourceReference()
50 bool destroyed; variable
/frameworks/base/docs/html/training/basics/activity-lifecycle/
Drecreating.jd33 <p>There are a few scenarios in which your activity is destroyed due to normal app behavior, such as
39 <p>When your activity is destroyed because the user presses <em>Back</em> or the activity finishes
45 saved data that describes the state of the activity when it was destroyed. The saved data that the
49 <p class="caution"><strong>Caution:</strong> Your activity will be destroyed and recreated each time
56 into an {@link android.widget.EditText} object). So, if your activity instance is destroyed and
66 event that your activity is destroyed unexpectedly so you can add additional information to it. Then
67 if the system must recreate the activity instance after it was destroyed, it passes the same {@link
77 If the activity is destroyed and the same instance must be recreated, the system passes the state
120 <p>When your activity is recreated after it was previously destroyed, you can recover your saved
130 that was destroyed.</p>
[all …]
Dstopping.jd128 other state data in case your activity is destroyed and recreated).</p>
140 the activity was previously stopped, but not destroyed.</p>
191 additional threads are destroyed and other long-running actions like method tracing are also
Dindex.jd71 <dd>Learn what happens when your activity is destroyed and how you can rebuild the activity
Dstarting.jd264 <p>Most apps don't need to implement this method because local class references are destroyed
/frameworks/base/services/java/com/android/server/am/
DEventLogTags.logtags50 # An activity is being destroyed:
67 # A service is being destroyed
/frameworks/base/docs/html/training/camera/
Dcameradirect.jd113 // underlying surface is created and destroyed.
246 preview surface destroyed is a pretty good hint that it’s time to stop the
252 // Surface will be destroyed when we return, so stop the preview.
/frameworks/base/docs/html/guide/components/
Dactivities.jd66 is popped from the stack (and destroyed) and the previous activity resumes. (The back stack is
91 the activity is being created, stopped, resumed, or destroyed. The two most important callback
103 activity (though it does not always mean the activity is being destroyed). This is usually where you
110 to be stopped and even destroyed. All of the lifecycle callback methods are discussed later, in
423 // The activity is about to be destroyed.
553 may happen because it is being destroyed, or because another activity
565 <td>Called before the activity is destroyed. This is the final call
619 android.app.Activity} object is destroyed, so the system cannot simply resume it with its state
622 that the system destroyed the activity and recreated it and, thus, probably
644 focus with its state intact: either the activity is destroyed, then recreated and the activity must…
[all …]
Dservices.jd81 can run in the background indefinitely, even if the component that started it is destroyed. Usually,
91 but when all of them unbind, the service is destroyed.</dd>
165 <dd>The system calls this method when the service is no longer used and is being destroyed.
281 the component that started it is destroyed. As such, the service should stop itself when its job
296 destroyed.</p>
724 that you pay close attention to how your service is created and destroyed, because a service
727 <p>The service lifecycle&mdash;from when it's created to when it's destroyed&mdash;can follow two
806 // The service is no longer used and is being destroyed
Dtasks-and-back-stack.jd98 button, the current activity is popped from the top of the stack (the activity is destroyed) and the
111 destroyed and the previous activity resumes.</p>
180 destroyed. The previous activity in the stack is resumed. When an activity is destroyed, the system
198 the state of your activities using callback methods, in case the activity is destroyed and must
415 destroyed and this intent is delivered to the resumed instance of the activity (now on top),
Dbound-services.jd13 <li>A bound service is destroyed once all clients unbind, unless the service was also started</li>
547 <p>When your client is destroyed, it will unbind from the service, but you should always unbind
625 two of those activities, the service may be destroyed and recreated as the current activity unbinds
Dprocesses-and-threads.jd69 components running in the process that's killed are consequently destroyed. A process is started
367 when the activity is destroyed, see the source code for the <a
Dfragments.jd74 fragments in it, and when the activity is destroyed, so are all fragments. However, while an
175 fragment (though it does not always mean the fragment is being destroyed). This is usually where you
484 destroyed when the transaction is committed and the user cannot navigate back to it. Whereas, if you
Dfundamentals.jd109 and has a distinct lifecycle that defines how the component is created and destroyed.</p>
/frameworks/base/docs/html/training/basics/fragments/
Dfragment-ui.jd165 to the back stack, the fragment that is removed is stopped (not destroyed). If the user navigates
167 stack, then the fragment is destroyed when removed or replaced.</p>
/frameworks/base/docs/html/guide/topics/resources/
Druntime-changes.jd47 process may have been destroyed. To learn how you can restore your activity state, read about the <a
248 destroyed before the user returns to it.</p>
/frameworks/base/docs/html/training/displaying-bitmaps/
Dcache-bitmap.jd182 destroyed. Once the user resumes, your application it has to process each image again.</p>
/frameworks/base/docs/html/training/basics/network-ops/
Dmanaging.jd325 // Unregisters BroadcastReceiver when app is destroyed.
/frameworks/base/docs/html/guide/practices/ui_guidelines/
Dactivity_task_design.jd443 destroyed. Starting Email again from its icon would simply bring the
466 destroyed when <em>Back</em> is pressed. When the user starts playing music in
469 destroyed, and continues playing music, even though its activity is no
/frameworks/base/docs/html/tools/testing/
Dactivity_testing.jd191 activity to be destroyed, so you should test that accidental device movements don't
/frameworks/base/docs/html/guide/basics/
Dappmodel.jd169 be destroyed and a new instance started.</p>
/frameworks/base/docs/html/guide/topics/ui/
Dmenus.jd600 action mode is destroyed. In the next step, you'll see how it's initialized and how saving
945 application is destroyed. If you have application settings that you would like to save for the user,
/frameworks/base/docs/html/guide/topics/graphics/
D2d-graphics.jd149 …out the underlying {@link android.view.Surface}, such as when it is created, changed, or destroyed.
/frameworks/base/docs/html/guide/topics/manifest/
Dactivity-element.jd317 activity is ignored. The activity is not re-parented, but destroyed.

12