cocos2d for iPhone

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

1. 

   chrisco
   Member

   For some reason, a schedule that I've set up isn't working. The method I'm trying to call is set up as follows:

   - (void)test:(ccTime)dt {
   	NSLog(@"test");
   }

   and I'm calling the schedule in my -init method of my subclassed scene as follows:

   [self schedule: @selector(test:) interval:0.5f];
   NSLog(@"%@", scheduledSelectors);

   The log directly following my setup of the schedule prints ""test:" = <Timer = 00E7CB50 | target:TPGameScene selector:(test:)>;", so I know that the schedule is "scheduled". However, the log statement in my scheduled method never prints.

   Has anyone come across this before?
   Thanks in advance!

   Posted 2 years ago #
2. 

   chrisco
   Member

   This has been solved (sort of). For some reason, copying the code into a new file with a different class name fixed the problem...

   Posted 2 years ago #
3. 

   Osiris
   Member

   I'm having the same problem all the sudden.

   I am firing off the same schedules I have in my production copy, but immediately after successsfuly renaming this test version, the schedules stoped scheduling. I didnt change anything in my source. I added the same Log as above immediately after the schedule to track it and get this:

   2009-09-29 07:57:06.049 Spirus Test[2352:207] {
       "addMonster:" = <Timer: 0x176260>;
       "addPowerUp:" = <Timer: 0x176440>;
       "checkLives:" = <Timer: 0x1763e0>;
       "step:" = <Timer: 0x1762a0>;
   }

   So they look like they are supposed to be firing, but nothing happens. The music starts playing but nothing moves.

   Posted 2 years ago #
4. 

   bradparks
   Member

   I don't know if this could be it or not, but for a node to be able to schedule a callback, it or one of it's parents has to be part of the scene.

   So make sure your node is part of the scene... (ie it or a parent node of it has scene.addChild(myNodeThatSchedulesACallback)

   Possibly it could be that the selector for your method is now nil because of a name change, but I don't know if that would just fail silently or not... I think it would since nil is allowed in alot more cases in Objective C than in most other languages, but I can't say for sure!

   Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.