cocos2d for iPhone

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

1. 

   thyrgle
   Member

   I am working on a game in Cocos2d for iPhone.

   In my init method I have an object (type id) declared as follows (also note bossDir is declared as 1):

   bossMov = [CCMoveTo actionWithDuration:1.0f position:ccp(75*bossDir, 320-55)];
       [boss runAction:bossMov];

   Then in a timer method I have:
   

   if ([bossMov isDone] == YES) {
       bossDir = -bossDir;
       [boss stopAllActions];
       [boss runAction:bossMov];
   }

   It moves the boss once, but after that it gives EXC_BAD_ACCESS and points me to a line in the file "CCTimer.m" that says:
   

   if( elapsed >= interval ) {
       impMethod(target, selector, elapsed); //This line in particular.
       elapsed = 0;
   }

   How can I fix this problem?

   Posted 1 year ago #
2. 

   michaelm
   Member

   The action is released after you stop actions. Either retain it or preferably recreate it when you need it.

   Posted 1 year ago #
3. 

   wilczarz
   Member

   Unless you have a good reason to make the action global, I'd recreate it every step of the way. From my experience it is never a good idea to retain autoreleased objects. You can always use condition: [boss numberOfRunningActions] == 0 instead of [bossMov isDone]. I think you can also add your action to a scene as a subnode and retrieve it later by tag - I haven't tried it but the action should be retained in that scenario. Cheers!

   Posted 1 year ago #
4. 

   spadict
   Member

   @wilczarz I'm not sure what an autoreleased object is good for if you never retain it, that really limits their scope to within a single function. Considering that both Cocoa and Cocos2D return a lot of autoreleased objects, I think you are expected to retain them.

   @thyrgle what are the properties of bossMov? If they are set as '(nonatomic, retain)' then your primary problem here is that you are missing the very important 'self.' in front of bossMov when you originally set it. If you don't use the 'self.' notation, you are directly setting the variable without putting it through the getter/setter which is where the retain in question happens.

   Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.