cocos2d for iPhone

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

1. 

   Freddy
   Member

   Hi, just stated learning cocos2d and found an issue I can't resolve.

   I'm creating a MultiplexLayer with some layers in it, each layer calls a method to do a CCFadeIn on init, everything fine here.

   Next I save a reference to those layers into a NSMutable Array so I can call a custom method on each layer after switching to it

   So far so good, a NSLog trace inside the method shows it gets called correctly but CCFadeIn won't run a second time

   .h code:

   @interface layer1 : CCLayer {
   
   	CCSprite *pic;
   }
   //
   -(void) fadeLayer;
   
   @end

   .m code:
   

   - (id) init{
       if( (self=[super init] )) {
           pic = [CCSprite spriteWithFile:@"layer1.png"];
   	pic.position = ccp(0,0);
           [self addChild:pic];
   	[self fadeLayer];
   	NSLog(@"init layer 1");
       }
       return self;
   }
   - (void)fadeLayer {
           //everything runs ok on init, only NSLog works on next calls
   	NSLog(@"fade in Layer 1");
   	[pic setOpacity:0];
   	[pic runAction: [CCFadeIn actionWithDuration:1.5]];
   
   }

   Any help is appreciated.

   Posted 1 year ago #
2. 

   mmilo
   Member

   Not sure what's wrong with your code in particular, but I think I ran into a similar problem. Here's an example:

   NSArray *myLayers; // contains your layers
   id action1 = [CCFadeOut actionWithDuration:1.0f];
   for (CCLayer *layer in myLayers)
   {
     [layer runAction:action1]; // weird, this only fades the first layer
   }

   I found I had to do something like:
   

   NSArray *myLayers; // contains your layers
   id action1 = [CCFadeOut actionWithDuration:1.0f];
   for (CCLayer *layer in myLayers)
   {
     id actionCopy = [action1 copy];
     [layer runAction:actionCopy]; // hopefully all my fades work!
   }

   Posted 1 year ago #
3. 

   Freddy
   Member

   Thanks mmilo and sorry for the delay to check your answer... sometimes the job gets on the way :)

   I tried it your way without luck, but I think I found a hint to the problem:

   if I switch the layers fast enough, the fade action(running the first time on init) is stopped and each layer keeps the alpha amount it had when doing the switch.

   So probably, the next time I switch a layer the method gets called too soon and before the switch is finished so the action actually tries to run but the switch overrides it.

   Right now my calls to the custom methods are done like this:

   //multiLayer == CCMultiplexLayer
   //current_page== page number
   [multiLayer switchTo:current_page];

   //pagsArray== array with reference to each layer
   [[pagsArray objectAtIndex:current_page] fadePage];

   Is there a way to check if switchTo has finished before calling my custom methods?, it looks like that's what I need to fix this.

   Thanks

   Posted 1 year ago #
4. 

   mmilo
   Member

   Try taking a look at the onEnter callback for CCNode.

   Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.