cocos2d for iPhone

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

1. 

   Metric
   Member

   Is it just me or does the debug version of the simulator not support writing out to the User Preference?

   For Example

   -(void) save {
   	NSUserDefaults *pref = [NSUserDefaults standardUserDefaults];
   
   	[pref setObject:[NSKeyedArchiver archivedDataWithRootObject:self] forKey:@"food"];
   	[pref synchronize];
   }
   
   -(void) load {
   	NSUserDefaults *pref = [NSUserDefaults standardUserDefaults];
   
   	NSData *dbObject = [pref objectForKey:@"food"];
   
   	if(dbObject != nil)
   	{
   		self = [[NSKeyedUnarchiver unarchiveObjectWithData:dbObject] retain];
   	}
   
   	[dbObject release];
   }

   Yes, I do have the proper initWithEncoder and encodeWithEncoder methods for the class. It compiles fine and seems to run through them just fine, except it never is able to reload the object from the key. Basically, dbObject is always returning nil, even though it saves properly.

   If anyone has any other suggestions on how to store the data besides the user preferences, please let me know. I am open to all suggestions on how to store data for between sessions.

   Posted 2 years ago #
2. 

   natanavra
   Member

   EDIT: Sorry, my bad, I posted something not too true about the topic...

   EDIT2: Have you tried retaining the object after retrieving, or retaining before saving? just a guess.

   EDIT3: Try using this function (non user defaults) to see if the data gets saved properly:

   + (BOOL)archiveRootObject:(id)rootObject toFile:(NSString *)path;

   ~ Natanavra.

   Posted 2 years ago #
3. 

   Metric
   Member

   I did some further debugging. It looks to be saving and loading now, but for some reason when I get to the actual game scene the data has reset. Now, my question is does cocos use the init method of the new scene everytime when the scene is replaced? If so, I wouldn't think that would cause a problem, because I still load it before the game scene appears.

   I don't have access to my mac mini to do further debugging to see what is happening at the moment.

   Posted 2 years ago #
4. 

   Lam
   Member

   It's more of a 'did you call [SomeCocoaScene node]?'
   Because if you did then init will be called.
   Replace doesn't call init.

   Posted 2 years ago #
5. 

   Metric
   Member

   That is what baffles me. I only ever call the constructor once through out the entire time.

   Basically it goes in this order -

   cocos launches->splash screen launches->app bridge launches from splash
   ->actions is called once with [actions node]->action loads the data
   ->app bridge then initialize menu->app bridge initializes other scenes->passes actions object reference to scenes
   ->cocos replace scene to menu screen->player presses play->cocos replaces with actual game scene

   I make sure that each scene / object is only ever created once to cut down on resources. Thus, each scene is only initialized once with [class node]

   Posted 2 years ago #
6. 

   Lam
   Member

   Oh ok.

   Do you store the [class node], holding it for later use?

   Posted 2 years ago #
7. 

   Codemattic
   Moderator

   Assigning self to something outside of an init method seems strange to me. Self already points to an object, so it leaks a little bit. Probably not the error thats losing your data, but it seems like not a Cocoa thing to do, but Im not sure if its a bug or not.

   There so much going on we arent seeing its hard to start guessing. You are archiving, but you know cocos objects arent serializeable yet - so I hope you arent archiving any cocos objects directly. What is self here? A Scene subclass?

   Posted 2 years ago #
8. 

   Metric
   Member

   Lam, yes I store it for later use.

   Codematic, the encoder class allows you to serialize certain apsects of your class. Each class to be encoded has to implement the encodeWithEncoder method, and initWithEncoder. The encoder method tells the encoder object of which data you wish to serialize from the class. The initWithencoder initialze the class with a coder object so you can decode from data or decode from file. Then you store the decoded items back into your class variables.

   Therefore when I do the decode it should return a new object. Therefore you are probably right about a memory leak when assigning self = the new object.

   However, that was a bad sample of only one of these in my code.
   Others load function first creates a temporary object that is directly initialed be the decoded object.
   Then, I transfer the variable values, and then release the temporary object.

   But still, even the ones that do it the proper way still seems to have the variables reset upon loading the game scene. The problem is quite odd, because each object is only ever initialized once.

   I know the object can hold the data across multiple scenes, because I can play till game over and see my stats on the next loaded scene just fine. The problem only occurs when it is first loading the application.

   Also, I don't load the previous data until everything is initialized. All my data objects lie in the actions class. Doing this keeps the data independent of the scene. All the scenes do is handle the graphics, taps, and menus.

   Posted 2 years ago #
9. 

   Metric
   Member

   Thanks codematic for spotting that mem leak.

   It seems that one mem leak was what was causing it to not load properly.

   Posted 2 years ago #
10. 

    Codemattic
    Moderator

    Cool! Whew, glad we got that.

    Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.