![]() ![]() That is, when designing the navigation, if you have screen A and you want the user to be able go to a subsequent screen B and then use the BACK key to go back to screen A, then the screen A needs to be implemented as an activity. The user can get to tasks earlier than the most recent Home by selecting its root activity from the application launcher, a shortcut, or the "Recent tasks" screen.Īctivities are the only things that can be added to the activity stack - views, windows, menus, and dialogs cannot. The adding of an activity to the current stack happens whether or not that activity begins a new task (as long as that task was started without going Home), so going back can let the user go back to activities in previous tasks. However, the user cannot use the BACK key to go back further than the last visit to Home. In general, when a user starts a new activity, it is added to the activity stack, so that pressing BACK displays the previous activity on the stack. This is the activity stack, also known as the back stack. However, the documentation assumes there will always be a Back key that the OS responds to:Īs the user moves from activity to activity, across applications, the Android system keeps a linear navigation history of activities the user has visited. ![]() I haven't been able to find any definitive answer one way or another. ![]()
0 Comments
Leave a Reply. |