Dianne, Firstly, many thanks for your reply!
> (1) This is a debugging feature, not something to turn on for normal > production. I understand this. > (2) It doesn't finish the activity; it destroys the current instance, which > will thus needed to be re-instantiated the next time the user navigates to > it (thus providing a way to test the state save/restore mechanism of > activities). thank you for pointing out the difference; I probably was expecting "finishing the activity" and "destroying the instance" to mean the same thing. > (3) There isn't a taboo about actually finishing an activity when it becomes > invisible... if that is the user interaction you want, go for it I guess, > though it might be a bit weird. (But finishing an activity after starting > another one, effectively making it disappear after the user leaves it, is a > very common and useful pattern.) I believe you :) > No users should EVER have this turned on. And I believe this is an > unprotected system setting so it would be possible for an application to > turn it on... but dear ghod do not do that, and the instance we hear about > any app doing that we will need to do something to prevent it. This is not > at all, ever, ever, something you should be running a device with for normal > usage. thanks for the warning; cheers! -- 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
