CODEWITHSUNDEEP
cocos2d-iphone
Duck
Duck

Reputation: 36013

runAction do not works for sprites coming from CCSpriteBatchNode

I am using Cocos2d 2.1rc0.

I have this project that was working perfectly when I was not using CCSpriteBatchNode. Then I decided to use batch nodes to reduce draw calls and my problems started.

A lot of stuff is not working well. reorderChild is one. Another one is runAction and without runAction Cocos is useless.

This is an example of a method that works without batchNodes and do not work with it.

// move/rotate all objects

for (int i=0; i<[allObjects count]; i++) {

        Card *object = [allObjects objectAtIndex:i];
        [object stopAllActions];

        CGPoint center = object.position;
        center.x = center.x + 100;
        center.y = center.y - 200;

        CCMoveTo *moveAction = [CCMoveTo actionWithDuration:0.3f position:ccp(center.x, center.y)];
        CCRotateTo *rotateAction = [CCRotateTo actionWithDuration:0.3 angle:0.0f];

        CCSpawn *action = [CCSpawn actions:moveAction, rotateAction, nil];

        [object runAction:[CCSequence actions: action,
                             [CCDelayTime actionWithDuration:0.1f],
                             nil]];
}

Exactly nothing happens.

I have tried to eliminate the CCSpanw and use runAction directly just with move and nothing works. If I use regular sprites, it works.

Objects in that array derive from a CCSprite based class.

Is there any workaround?

Upvotes: 0

Views: 593

Answers (2)

CodeSmile
CodeSmile

Reputation: 64477

After double-checking in a clean project that this isn't a weird side-effect of some kind, I have to say there's something fishy about your project. Hard to tell what, though.

What I did: create a sprite-batch, add a sprite to it, also store it in an array. In a scheduled method I'm receiving the sprite from the array (not casting) and run your action sequence posted above. It works fine, as expected.

The casting should not make any difference. Batched or non-batched sprite should not make any difference either.

If it does, something really weird is going on. After all the card object is the same with or without casting. If it were not actually running the runAction method, you'd be receiving an "unrecognized selector sent to instance" error. But that's not the case.

Try again without casting, after rebooting your device, your machine, cleaning the project in Xcode and rebuilding. Also test in debug and release configurations. I've had the weirdest issues that were gone after doing one of the above, and definitely all of the above. If that doesn't fix things, you can be sure it's a problem with the code (memory leak is my alltime favorite) or the project settings (ie uncommon compiler optimizations sometimes can have side-effects).

Step into the runAction method if it really doesn't run the action - I'm sure it will add the action to the action manager. Try with and without casting to see if there really is a different code path taken. I doubt it.

Upvotes: 0

Duck
Duck

Reputation: 36013

the solution is to cast the class to the object extracted from the array...

instead of

Card *object = [allObjects objectAtIndex:i];

this

Card *object = (Card *)[allObjects objectAtIndex:i];

Upvotes: 1

Related Questions