Just adding some more info here for any who follow - this only happens in one of our games, and the major difference is that the game with the problem has it's screen orientation locked to landscape mode. Since the home screen intent view appears in portrait orientation I suspect this is causing the problem somehow. We still should be receiving a proper onPause() before being killed, but maybe because we've requested a permanent landscape mode these events aren't being triggered properly.
Matt On Mar 10, 3:22 pm, Matt Hall <matt.h...@gmail.com> wrote: > Hi everyone, > > When we're in inPause() in our games we do a few things like stop > animations, which normally works perfectly. However, when an app is > installed on the phone that causes an intent popup, like a home screen > replacement (aHome is what I'm using to test), then in the onPause() > suddenly our field variables are null and our game null pointers when > trying to stop the animations. As a nasty side effect, this causes a > force close loop between our game and the intent handling window. > > Has anyone else seen this? For now I'm going to catch and ignore that > null pointer, but from the activity life cycle information this > situation makes no sense to me. > > Thanks very much for any help/info, > Matt --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
