On Wed, Jun 18, 2014 at 2:16 PM, 'RLScott' via Android Developers < [email protected]> wrote:
> I was going to have each instance storing its place in the tree (as a path > name) so that I could "pop" this stack all the way to the beginning. But > then I remembered the Activity life cycle, and the fact that Android can > destroy any activity that is not visible. So that would trash my stack, if > the stack was stored as instance data for each instance of the File > Explorer. > Do I have that right? No. The system maintains the stack, regardless of whether activities within that stack have been killed. If you pop back up to a previous activity that was destroyed, the system will re-create it. If you handle the Activity lifecycle correctly, this should appear as though the Activity was never destroyed to the user. > And if so, what is a preferable way to manage a stack of nested > instances of a File Explorer activity? Although pushing multiple instances of the Activity will work, you can obviously very quickly end up with an excessive number of Activities. I think Kostya's suggestion is the way to go. ------------------------------------------------------------------------------------------------- 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 [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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
