cocos2d for iPhone

A fast, easy to use, free, and community supported 2D game engine

1. 

   crmagicxxx
   Member

   Just to warn you all that applicationWillTerminate: will not be called on multitasking devices if app is suspended and then killed via the multitasking UI. According to Apple: "apps are not aware of any transitions into or out-of the suspended state". So if you're saving anything inside applicationWillTerminate: you better do it in applicationWillResignActive: also.

   Best

   Edit:
   Reference - https://devforums.apple.com/message/239897#239897

   Posted 1 year ago #
2. 

   jyoung
   Member

   Alternatively, from Apple documentation, "you can explicitly opt out of the background execution model by adding the UIApplicationExitsOnSuspend key to your application’s Info.plist file and setting its value to YES."

   Posted 1 year ago #
3. 

   crmagicxxx
   Member

   Yes you can, but I am sure users will adopt that "quasi multitasking" very soon and you'll get bad reviews if your app goes away like that...

   Posted 1 year ago #
4. 

   Codemattic
   Moderator

   thanks @crmagicxxx - I would of guessed that -applicationWillTerminate: would be called, it seems wrong that it doesnt, you *are* terminating. -applicationWillResignActive: it is then.

   Posted 1 year ago #
5. 

   jyoung
   Member

   magic, you bring up a good point. I was going to disable my game from going into the background since it is a game..

   "Opting out of background execution may be preferable for certain types of applications. Specifically, if coding for the background may require adding significant complexity to your application, terminating the application may be a simpler solution. Also, if your application consumes a large amount of memory, the system might need to terminate your application quickly anyway to make room for other applications. Thus, opting to terminate, instead of switch to the background, might yield the same results and save you development time and effort."

   But now I'm rethinking this. I guess I'll have to get it on the device and see for myself.

   I'd be interested to know what other developers think about suspending games in iOS4?

   Posted 1 year ago #
6. 

   Codemattic
   Moderator

   "I was going to disable my game from going into the background since it is a game.." if you do, please save your game state so when I restart your game it brings me back to where I was. Best thing short of multitasking.

   Posted 1 year ago #
7. 

   jyoung
   Member

   @Codemattic done :)

   I just don't know if it's worth keeping the entire app in memory in the background.

   Posted 1 year ago #
8. 

   jptsetung
   Member

   "Also, if your application consumes a large amount of memory, the system might need to terminate your application quickly anyway to make room for other applications."

   That means that you don't risk anything to implement the background state with the director stopAnimation method.

   Posted 1 year ago #
9. 

   PJX
   Member

   I copied my state saving code from applicationWillTerminate to applicationDidEnterBackground and also added a multitaskingEnabled boolean so that I only call state saving in applicationDidEnterBackground. BECAUSE, there is one instance on a multitasking device where applicationWillTerminate is called: If the app is in the foreground and you power off the device. In that case, both applicationDidEnterBackground and applicationWillTerminate get called.

   My question really is not about saving state, it's about releasing Cocos2D: Where do we call 'end' on the CCDirector object? Is this creating a huge memory leak?

   Some things about iOS really make no sense and this applicationWillTerminate thing is one of them.

   Regards, Patrick

   Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.