On Sat, Dec 22, 2012 at 8:06 PM, Mark Murphy <[email protected]>wrote:
> > That is a documentation flaw. Android does not "destroy this instance > of the activity to save space", except by terminating the entire > process. isFinishing() will distinguish multiple reasons for onPause() > and onStop() being called (e.g., BACK will cause isFinishing() to > return true, HOME will cause isFinishing() to return false). That's strange. What I see in an Activity that initialises some static data in its onCreate() is that occasionally, the statics are initialised already when onCreate() starts to execute. I thought this was a sign that a previous instance of the Activity (the one that initialised the static data presumably) had been destroyed but the process was not. Is there a better explanation? -- 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
