cocos2d for iPhone

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

1. 

   Wayfarer
   Member

   I'm looking for a reasonably technical explanation of how scheduling (and more specifically) unscheduling works in coocs2d. The reason I'm asking is in my program I have some sprites appear on the screen, at which point I have them schedule themselves to die in 5 seconds. However, if you touch them they are "saved" and I call "unschedule" on them, to stop their death method.
   

   [self schedule: @selector(dotSuicide:) interval:theLifeSpan]; //This causes it to die
   		[self schedule: @selector(fadeOut:) interval:(theLifeSpan - kdotFadeTime)]; //This causes it to fade out

   And then:

   [theSprite unschedule:@selector(fadeOut:)];
   [theSprite unschedule:@selector(dotSuicide:)];

   However, the unscheduling doesn't seem to be working properly, or not *all the time*, and so I'm trying to get a little deeper into this issue to figure out what's happening.

   Thanks!

   Posted 1 year ago #
2. 

   crmagicxxx
   Member

   Maybe you didn't get it that calling schedule at interval doesn't call it only once, but periodically at that interval. So check your dotSuicide: and fadeOut: methods and make sure you also unscheduled them there

   Posted 1 year ago #
3. 

   Wayfarer
   Member

   They do:

   -(void)fadeOut: (ccTime) delta {
   	[self runAction:[CCFadeOut actionWithDuration:kdotFadeTime]];
   	[self unschedule:@selector(fadeOut:)];
   }

   And:

   -(void)dotSuicide:(ccTime)delta {
   	[self.engine.dotsOnScreen removeObjectIdenticalTo:self];
   	[self.parent removeChild:self cleanup:YES];
   }

   I don't call it in dot suicide, because as it says here, the timers deactivate when the node has left (in this case, removed.)

   Those methods go off if the user did NOT touch the sprite. When the user HAS touched the sprite, it should cancel the two schedulers and the sprite should not fade out and die. But it does.

   Posted 1 year ago #
4. 

   riq
   Key Master

   unschedule should always unschedule scheduled selectors. If it doesn't, then it is a bug. If so, could you open a ticket with the test case to reproduce it ? Thanks.

   Posted 1 year ago #
5. 

   remover
   Member

   i think the scheduling system in cocos2d is a little flunky. i think 99.3 or 99.2 tries to address some of these issues. i have had some problems myself with schedulers going 'crazy' - suddenly firing much more rapidly than they have been scheduled. if you look around on this forum you'll find similar issues.

   i'm still using 99.0 so not sure how good the later versions are in relation to these issues.

   Posted 1 year ago #
6. 

   riq
   Key Master

   @remover: v0.99.3 has a new scheduler

   Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.