On Sat, Jan 15, 2011 at 2:35 PM, Kevin Duffey <andjar...@gmail.com> wrote:
> I thought you weren't really supposed to "quit" an app? > Right - but you should "back out" of your app and make sure whatever lifecycle methods you're handling work correctly. > But I thought by listening to the activity events of pause/resume, and so > forth you can use those to exit the app gracefully? > Precisely - it's these methods one should be testing when entering and leaving the app. > For that matter, since games use threads, don't they have to stop the > threads, save state, and such when a user presses home to exit out of it? > Ideally - I would assume a game would enter some "paused" state. > Lastly, I thought we're never to try to block the home button? I didn't > even know that was possible. > It's not. ------------------------------------------------------------------------------------------------- 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 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
