The best way I have found to handle this is: be ready to be killed _in_any_moment_. This may seem unlike to happed, but still you must be ready. How? By saving your state when your onSavedInstanceState() is called, gracefully releasing resources when onDestroy() is called, and restoring the state when onCreate() is called.
This is a superset of the problem that you are describing, but I have found to be easier to think in this way than trying to solve every particular scenario. On 2 abr, 09:58, b_t <bartata...@gmail.com> wrote: > Hi, > > Maybe an easy question. > > When activity A launches activity B then it is possible that A > destroyes before the user navigates > back from B? So A will be recreated and don't remain object state? > > T. -- 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
