On Fri, Jul 2, 2010 at 3:38 PM, david2 <[email protected]> wrote: >> onPause() is called whenever the activity loses the foreground from an >> input standpoint. >> >> onStop() is also called, if the activity is no longer visible on the screen. >> >> onDestroy() is also called, if the activity instance is going away for good. >> >> Hence, BACK calls onPause(), onStop(), and onDestroy(). HOME calls >> onPause() and onStop(). > > Not true. Back does not call onDestroy.
Yes, it does. > On destroy is called when the > system decides the application is going away. Such as when the user presses the BACK button. > This does not normally > occur on a back button or home button. Yes, it does normally occur on a BACK button. > Processes stay around until > memory is needed elsewhere. Which has little to do with onDestroy() of individual components within that process. > And even then, documentation states that > onDestroy may never get called even when the application is killed. Correct. > In general BACK doesn't do anything additional vs. HOME. Yes, it does. It causes the activity to be destroyed. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training...At Your Office: http://commonsware.com/training -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
