Lines Matching refs:back
24 <li><a href="#Clearing">Clearing the back stack</a></li>
64 when performing a certain job. The activities are arranged in a stack (the "back stack"), in the
70 <h3>Adding fragments to a task's back stack</h3>
72 <p>Your activity can also include {@link android.app.Fragment}s to the back stack. For example,
76 desireable for the user to navigate back to reveal fragment B, using the <em>Back</em> button.</p>
77 <p>In order to add fragment B to the back stack so that this is possible, you must call {@link
81 <p>For more information about using fragments and adding them to the back stack, see the {@link
102 the back
104 this behavior with a timeline showing the progress between activities along with the current back
109 task adds an item to the back stack. When the user presses the <em>Back</em> button, the current
132 stopped, but the back stack for the task remains intact—the task has simply lost focus while
144 this point, the user can also switch back to Task B by going Home and selecting the application icon
153 <p>Because the activities in the back stack are never rearranged, if your application allows
195 stopped. This way, when users navigate back to a previous activity, its user interface appears
204 knows that the activity has a place in the back stack, but when the activity is brought to the
218 <p>The way Android manages tasks and the back stack, as described above—by placing all
221 with tasks or how they exist in the back stack. However, you might decide that you want to interrupt
225 instance on top of the back stack); or, you want your back stack to be cleared of all
261 flags to define how activities are associated with tasks and how the behave in the back stack.</p>
267 launch and when navigating back to it from other activities and tasks with the <em>Back</em> button.
322 activity at the top of the back stack is <em>not</em> an existing instance of the activity).
323 <p>For example, suppose a task's back stack consists of root activity A with activities B, C,
368 point, the back stack now includes all activities from the task brought forward, at the top of the
373 launch mode "singleTask" is added to the back stack. If the activity is already a part of a
374 background task with its own back stack, then the entire back stack also comes
405 <dd>If the activity being started is the current activity (at the top of the back stack), then
461 back stack as the caller. However, if the intent passed to {@link
470 it, there must be some way for the user to navigate back to the task. Some entities (such as the
475 back to the task that's started, such as with a launcher icon (the root activity of the task
501 <h3 id="Clearing">Clearing the back stack</h3>
563 <p>This second ability is important: Users must be able to leave a task and then come back to it