I need to implement a File Explorer as an activity within my app. One of the functions of such an activity is the ability to recursively navigate up and down the directory tree. I was planning on doing that by having the current instance of the File Explorer start another instance of the File Explorer when then the user taps on a directory entry. 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? And if so, what is a preferable way to manage a stack of nested instances of a File Explorer activity?
-- 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 --- 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 android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
