Just let each activity worry about itself... Use onSaveInstanceState() and onRestoreInstanceState() in each activity and you should find that everything will work out just fine.
Thanks, Justin Anderson MagouyaWare Developer http://sites.google.com/site/magouyaware On Sun, Jun 3, 2012 at 5:02 AM, Blue Wanderer <[email protected]>wrote: > As it is said in the Dev Guide Activities could be *restored* after > "the App process is killed" and "User navigates to the Activity". > First of all, I have never seen this happened. It doesn't seem that I > can "navigates back" to an Activity when its process is killed, the > Activity is simply gone from the Activity stack after the process is > gone. > > If such thing is to happen, how exactly it will happen? > > And I saw a weird but good thing is that: > There is one Activity A1 which starts Activity A2 of another App. Now > A2 is the foreground activity. When memory gets low, at least on > emulators(where I can easily eat up the RAM), A2 will be killed > instead of A1. > > I will make cry if I have to restore all the relationships between the > Activities risen from the dust. > > -- > 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 -- 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
