I thought "finishing the activity when it becomes invisible" was a taboo (i.e. against the activity and Task design guidelines); however, I can imagine cases where not maintaining a History would help keep the memory footprint of the app low.
> Dianne Hackborn wrote: > Another thing you can do is use Dev Tools to turn on "Immediately destroy > activities" in its Development settings. This causes every activity to be > destroyed once it is no longer visible. (I assume you are achieving the > same thing here by having the activity dropped from the history stack... > though I could be totally wrong. :p) We would probably achieve the same thing on the device, we are developing on, but not every user will have this turned ON on their devices, right? -- 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
