Game Development Community

schedule return value question

by Amjad Yahya · in Torque Game Builder · 12/06/2011 (2:41 am) · 3 replies

I have this function that returns a true or false value like this:

%match=%obj.checkmatches();

but if I use a schedule function like this:

%match=%obj.schedule(500,"checkmatches");

the return value -as it says in the documentations- will return an event id value.

How can I solve this? I must use "schedule" and must know the return value.

Any ideas.

Thanks.
NextNext Thread
PrevPrevious Thread
More from Torque Game Builder


Conor O'Kane
cokane.com
#1
12/06/2011 (4:45 am)
Instead of returning the result - save it in a global variable, or if you're worried about it getting overwritten, stick it on the end of an array.

Torque 3D Owner Harry Durnan
#2
12/06/2011 (7:47 am)
Yes, I agree with Conor. You need to save off the result inside the checkmatches() function. It's probably easiest to use some a global variable, though depending upon exactly what you need to know you may want to stick it in some other structure. Then you can check %match against that global variable/structure instead.

Torque Owner Noby Nobriga
Quagga Games, LLC
#3
12/09/2011 (2:07 pm)
It depends on what you're trying to accomplish. You might want to consider rethinking things. Maybe scheduling another intermediate method. Then that method will call the actual checking method and handle the %match results. When you use something like schedule, it's usually a fire-and-forget within the scope of the current function.

If you "must use schedule," then here is one suggestion. Of course, I don't know exactly what you're wanting to do in your actual code.

function myFunction()
{
  %obj.schedule(500,"checkMatches");
  // Throw up a gui with text saying "checking for matches"
  matchesGui.Visible = true;
  matchesGui.status.text = "Checking for matches...";
  // .. continue doing other stuff
}

function MyObject::checkMatches(%this)
{
  %matches = %this.onCheckMatches();
  if (%matches)
  {
    matchesGui.status.text = "Matches found.";
  } else {
    matchesGui.status.text = "No matches found.";
    doSomethingHere();
  }
  // ... do other things with %matches here
}

function MyObject::onCheckMatches(%this)
{
  // ... do some stuff and get a true/false result
  return true;
}

In the above, you fire off the scheduled event and let other code take care of what it's supposed to do with the result. In the original function you continue doing your additional work that doesn't involve the result. The "checkMatches" function could be a global function instead of a member function on MyObject, depending on what you're trying to do.

You can keep checkMatches in a super class and override onCheckMatches for more specific subclasses/object.

Did I overly complicate things?