I can't make CCsequence work properly... please help.

cocos2d for iPhone » Programming » cocos2d support (graphics engine)

I can't make CCsequence work properly... please help.

(9 posts) (7 voices)

Started 1 year ago by romulobr
Latest reply from rozochkin

Tags:

romulobr
Member

When i call:

id actionNasce = [CCAnimate actionWithAnimation:nasce];
id actionCome=[CCAnimate actionWithAnimation:come];
id sequencia=[CCSequence actions:actionNasce,[CCRepeatForever actionWithAction:actionCome],nil];

I get this error: Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[CCRepeatForever duration]: unrecognized selector sent to instance 0xf44a60'

Am I doing something wrong? Isn't that supposed to work, if I remove any of the actions it works, but it doesn't when both are on the same CCAequence.

Posted 1 year ago #

I'm pretty sure this is documented that you cannot use a RepeatForever action inside of a sequence. And really it doesn't make sense because if you did repeat forever and had another action after it would never run.

I think you'll need to set it up with a callback in a sequence to begin your repeatForever action like:

id actionNasce = [CCAnimate actionWithAnimation:nasce];
id actionNasceComplete = [CCCallFuncN actionWithTarget:self selector:@(nasceComplete:)];

id sequence = [CCSequence actions:actionNasce, actionNasceComplete];
[someNode runAction:sequence];
...

- (void) nasceComplete:(CCNode *)aNode
{
    id actionCome=[CCAnimate actionWithAnimation:come];
    [aNode runAction:[CCRepeatForever actionWithAction:actionCome]];
}

Posted 1 year ago #

romulobr
Member

Thanks a lot, I knew it would be something simple. Sorry for the stupid question...

Posted 1 year ago #
romulobr
Member

Thanks a lot, I knew it would be something simple. Sorry for the stupid question...

Posted 1 year ago #
mobilebros
Moderator

Well, I'm going to use this post as an excuse to ponder.... why shouldn't you be able to use RepeatForever in a sequence IFF it's the last action in the sequence. Any takers?

Posted 1 year ago #
Nephilim
Member

Agreed with mobilebros. You should be able to use CCRepeatForever in a CCSequence, since you might want to do some things BEFORE you start something repeating forever. Most often, this will be useful for things such as doing "intro" animations to set up the thing being animated, such as triggering an endless idle animation after an entry animation, moving a sprite into view from offstage before beginning its looping movement, etc.

Anyway, romulobr, you can achieve (nearly) the same effect by using CCRepeat instead of CCRepeatForever, since CCRepeat does not run afoul of the aforementioned limitation. Just use INT_MAX as the number of times. Unless what you're animating is instantaneous, the player will quit the game long before INT_MAX times have been looped.

Posted 1 year ago #

Adam Allen
Member

A possible work around would be to have your CCSequence include your actionNasce and then pass it off to a selector:

id actionNasce = [CCAnimate actionWithAnimation:nasce];
id sequencia=[CCSequence actions:actionNasce,[CCCallFuncN actionWithTarget:self selector:@selector(nasceFinished:)],nil];
[your_sprite runAction:sequencia];

Inside of your nasceFinished selector, run your repeatForever actionCome:

-(void) nasceFinished {
 id actionCome=[CCAnimate actionWithAnimation:come];
[your_sprite runAction:actionCome];
}

This may not be proper optimization, but it is how I would hack it together.

Posted 1 year ago #

aruss
Member

this post helped me too :D

but, it would make more sense to allow inserting RepeatForever actions in to sequences and just ignoring the following actions because all of them derives from action class, it sounds more oop logical

Posted 1 year ago #
rozochkin
Member

Thank you

Posted 5 months ago #

RSS feed for this topic

Reply

You must log in to post.