That's what's throwing me for a loop. onDestroy is never called ...and I don't believe there's any reason it'd be killed off forcefully.
On Fri, Jul 2, 2010 at 3:31 PM, Mark Murphy <[email protected]> wrote: > On Fri, Jul 2, 2010 at 3:30 PM, Connick <[email protected]> wrote: > > However if I navigate elsewhere in > > the app via menu option then navigate BACK to the original screen via the > > menu, onCreate receives null for the incoming Bundle and my TextView > loses > > state. > > What caused 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 Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- 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
