That may be true, but if so, there is a serious problem with the online Android documentation. For as I have already shown, the documentation clearly states that there is a possible transition direct from the started state to the stopped state, one that does not call onPause() first.
So other than your own authority, on what grounds do you say that the docs are wrong? On Jul 2, 11:35 am, Mark Murphy <mmur...@commonsware.com> wrote: > On Fri, Jul 2, 2010 at 2:32 PM, Indicator Veritatis <mej1...@yahoo.com> wrote: > > But what about when the user presses the home key? According to the > > docs, onPause() is called WHENEVER the application goes invisible, not > > just on the Back key, not just when another application is launched. > > So no, it is not just on the Back key. > > 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(). > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://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 android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
