Lines Matching refs:destroyed

61 is popped from the stack (and destroyed) and the previous activity resumes. (The back stack is
86 the activity is being created, stopped, resumed, or destroyed. The two most important callback
98 activity (though it does not always mean the activity is being destroyed). This is usually where you
105 to be stopped and even destroyed. All of the lifecycle callback methods are discussed later, in
418         // The activity is about to be destroyed.
548        may happen because it is being destroyed, or because another activity
560    <td>Called before the activity is destroyed.  This is the final call
614 android.app.Activity} object is destroyed, so the system cannot simply resume it with its state
617 that the system destroyed the activity and recreated it and, thus, probably
639 focus with its state intact: either the activity is destroyed, then recreated and the activity must…
645 activity is destroyed, because there are cases in which it won't be necessary to save the state