Lines Matching full:tasks
1 page.title=Tasks and Back Stack
13 <li>Tasks can move to the background and retain the state of each activity in order for users
14 to perform other tasks without losing their work</li>
20 <li><a href="#ManagingTasks">Managing Tasks</a>
88 <p>The device Home screen is the starting place for most tasks. When the user touches an icon in the
121 class="img-caption"><strong>Figure 2.</strong> Two tasks: Task B receives user interaction
145 that started that task (or by touching and holding the <em>Home</em> button to reveal recent tasks
149 <p class="note"><strong>Note:</strong> Multiple tasks can be held in the background at once.
150 However, if the user is running many background tasks at the same time, the system might begin
158 times (even from different tasks), as shown in figure 3. As such, if the user navigates backward
163 href="#ManagingTasks">Managing Tasks</a>.</p>
166 <p>To summarize the default behavior for activities and tasks:</p>
182 <li>Activities can be instantiated multiple times, even from other tasks.</li>
217 <h2 id="ManagingTasks">Managing Tasks</h2>
219 <p>The way Android manages tasks and the back stack, as described above—by placing all
222 with tasks or how they exist in the back stack. However, you might decide that you want to interrupt
262 flags to define how activities are associated with tasks and how the behave in the back stack.</p>
266 behavior for activities and tasks. If you determine that it's necessary for your activity to modify
268 launch and when navigating back to it from other activities and tasks with the <em>Back</em> button.
280 should associate with tasks when it starts.</li>
316 each instance can belong to different tasks, and one task can have multiple instances.</dd>
322 belong to different tasks, and one task can have multiple instances (but only if the
