From 00697a90bec4e0536cfa0873602b64bb6785022e Mon Sep 17 00:00:00 2001 From: Roman Nurik Date: Fri, 16 Dec 2011 11:48:24 -0800 Subject: [PATCH] docs: Add missing intent flag to Android U nav class Change-Id: I18eb286a8d8b2c70f7d894d1244d2568ce6ce6c0 --- docs/html/training/design-navigation/ancestral-temporal.jd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/html/training/design-navigation/ancestral-temporal.jd b/docs/html/training/design-navigation/ancestral-temporal.jd index d12fd5caf0c77..02e43e150bd11 100644 --- a/docs/html/training/design-navigation/ancestral-temporal.jd +++ b/docs/html/training/design-navigation/ancestral-temporal.jd @@ -64,6 +64,6 @@ next.link=wireframing.html

In some cases, it's appropriate for Up to perform an action rather than navigating to a parent screen. Take for example, the Gmail application for Android 3.0-based tablets. When viewing a mail conversation while holding the device in landscape, the conversation list, as well as the conversation details are presented side-by-side. This is a form of parent-child screen grouping, as discussed in a previous lesson. However, when viewing a mail conversation in the portrait orientation, only the conversation details are shown. The Up button is used to temporarily show the parent pane, which slides in from the left of the screen. Pressing the Up button again while the left pane is visible exits the context of the individual conversation, up to a full-screen list of conversations.

-

Implementation Note: As a best practice, when implementing either Home or Up, make sure to clear the back stack of any descendent screens. For Home, the only remaining screen on the back stack should be the home screen. For Up navigation, the current screen should be removed from the back stack, unless BACK navigates across screen hierarchies. You can use the {@link android.content.Intent#FLAG_ACTIVITY_CLEAR_TOP} intent flag to achieve this.

+

Implementation Note: As a best practice, when implementing either Home or Up, make sure to clear the back stack of any descendent screens. For Home, the only remaining screen on the back stack should be the home screen. For Up navigation, the current screen should be removed from the back stack, unless BACK navigates across screen hierarchies. You can use the {@link android.content.Intent#FLAG_ACTIVITY_CLEAR_TOP} and {@link android.content.Intent#FLAG_ACTIVITY_NEW_TASK} intent flags together to achieve this.

-

In the last lesson, we apply the concepts discussed in all of the lessons so far to create interaction design wireframes for our example news application.

\ No newline at end of file +

In the last lesson, we apply the concepts discussed in all of the lessons so far to create interaction design wireframes for our example news application.