On Mon, Jan 10, 2011 at 6:15 PM, jotobjects <[email protected]> wrote:
> In the usual case of the Application only having one Process what part > of the application would not be stopped? > All of the state about the app is kept -- other activities the user has visited, running services, etc. The process may quickly be restarted due to this, or later be re-started in a different state to match them. > It seems that finish() is the better way so that the Android platform > can manage the process lifecycle, but finish() only stops one Activity > not all the components of the Application. The > FLAG_ACTIVITY_CLEAR_TOP from the launch Activity will stop the > Activities (if there is not more than one Task involved) but not the > Service components. It comes back to designing Apps that do not need > to be stopped. > Well, killing the process absolutely does not mean clean up the activity history. > The real world case I encountered recently was an App that required > registration and exited automatically if the user did not complete the > registration steps. This was done with finish(). Is there any better > way to accomplish that kind of requirement? > Use finish(). -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
