Cancelling All Scheduled Events

#1 Every time you create a scheduled event go like this:
$schedule[$numSchedules] = schedule(...);
$numSchedules++;

Then when you want to cancel them all go like this :

for (%c = 0; %c < $numSchedules; %c++)
{
// I don't know how to check if the scedule still exists though it doesnt really matter
cancel($schedule[%c]);
}

#2 Thats what I'm doing at the moment. I was just looking for a better way as otherwise I don't care about them. I thought it would be nice if I could just say to the Torque engine - kill all the scheduled events.

#3 Just put it in a function called cancelAllSchedules() ... then you have your own function to tell the engine to do that :)

#4 I think this thread is revealing just how lazy I am.... :)

#5 There is no mass schedule killer in the engine by default. It is trivial to add one however. Of course, doing so requires a recompilation of the engine, which probably makes Chris' solution the 'lazier' way to go. :) His is also generally better for reasons I'll mention below.

You'll need to add the following to console/simManager.cc around line 110:

void cancelAllPendingEvents()
{
   SimEvent **walk = &gEventQueue;
   SimEvent *current;
   
   while((current = *walk) != NULL)
   {
      *walk = current->nextEvent;
      delete current;
   }
}

Add the following to console/simBase.h at line 1270:

void cancelAllPendingEvents();

And finally, add the following to console/simBase.cc around line 435:

ConsoleFunction(cancelAllSchedules,void,1,1,"cancelAllSchedules()")
{
   argc;
   Sim::cancelAllPendingEvents();
}

This probably isn't in the code already because it is kind of dangerous. A lot of stuff uses schedules and this blows them *all* away without discrimination, so be careful. :) Keeping track of your schedules as Chris' script solution does is almost always the better thing to do.

#6 Oh, and you can check to see if a scheduleID is still pending by calling 'isEventPending(%scheduleID)' though don't bother to test if the event is pending before cancelling it, because both just walk the event queue the exact same way, one returning a value the other removing it if it exists.

#7 I'm convinced.

I'll stick with the script!

Thanks for all the replies.

#8 You can have all scheduled events associated with an object and then delete the object to cancel them.

objectName.schedule(9999, "functionName");
objectName.safeDelete();

Since objects are deleted when a level unloads, you can use this method to be sure that the schedules will be canceled.

#9 i think that another way to doit is, basically the same explained in the 1st post, but using simsets, since those are some kind of arrays that autoupgrade when a value of it is deleted, you just need to know how big the simset is, and off you go...