On Wed, Apr 27, 2011 at 2:52 PM, Eric <[email protected]> wrote: > However, when dealing with onPause(), onStop(), onDestroy(), it makes more > logical sense to perform your own work first (cleanup in onPause, > onDestroy(), BEFORE calling through to the superclass, which will > effectively invalidate your activity once you do that. >
I don't know what you mean by "effectively invalidate your activity", but it really shouldn't matter. Those methods are for you clean up after yourself - i.e., to stop / kill things that the base class does not know about nor will touch when it does its own cleanup business. It's not like super.onDestroy() wipes your Activity from memory - the rest of your function will execute allowing you to do what you need. Personally I always call super.X() first and so far so good. ------------------------------------------------------------------------------------------------- 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
