This is useful info for me, and I hope others. Sorry to be a pest but another question(s) for Those Who Know:
If you do a (nested) series of startActivtyForResult() (say 2-3) is the view hierarchy of the parent held in memory (yes, I think). If so, would a good strategy be to setContentView( null ) in onStop() of the invoker and put it back onStart() ? (At the expense of UI performance.) (Of course, I guess the right thing is to re-architect to not do this in the first place!) On another topic, does Resources flush its cache in low-memory conditions? -- Ward --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
