On Wed, Apr 27, 2011 at 4:55 PM, Eric <e...@alum.mit.edu> wrote: > It means the activity can be destroyed after onPause() by the system > calling 'finish()' on it. >
calling finish() will result in onStop() -> onDestory() when in the paused stated. It seems to me, in that specific case, if you've started another > activity from the current activity, and right after your onPause() was > called, Android decides 'finish' your activity due to memory constraints, > I don't see anything in the documentation that says Android can't 'finish' > your activity right there on the stop, thereby bypassing the call to > onStop(), and going directly into onDestroy(). > Where does it say the system "bypasses" onStop() and goes directly to onDestroy()? > In this case, the process would still be running, your activity would be > "paused", archived, and 'destroyed', but never 'stopped'. > No. The flow is pause -> stop -> destroy. There is no random skipping about. > You say 'onStop()' will _definitely_ be called. I don't see that in the > documentation I read. > Look at the pretty graph - it pretty clearly indicates the only way to onDestroy() is from onStop(). Honestly, I think you're over-thinking this and confusing yourself. ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
