| 12-18-2002, 10:53 PM | #1 |
We all know that WE's WAIT = TriggerSleepAction. So what do these functions do: Code:
native TriggerWaitOnSleeps takes trigger whichTrigger, boolean flag returns nothing native IsTriggerWaitOnSleeps takes trigger whichTrigger returns boolean I'm only guessing, but they could enable / disable full length sleeps for wait triggers on battle.net. Note that this is UNTESTED! I will try it later also. |
| 12-19-2002, 08:50 PM | #2 |
Did you ever test this? |
| 12-19-2002, 08:54 PM | #3 |
Not yet, I've been busy on one of my maps - I just noticed it while browsing through Blizzard.j. It'll be about a week or two before I can test it. |
| 12-22-2002, 01:08 AM | #4 |
^bump^ |
| 12-22-2002, 09:03 AM | #5 |
I haven't tested this and I don't think it's necessary to. Obviously these two triggers affect the Wait in triggers. The first one TriggerWaitOnSleeps takes a trigger and a boolean: false to disallow waits in a specified trigger, true to allow waits in a specified trigger. Similarly, IsTriggerWaitOnSleeps takes a trigger and returns a boolean: false if the specified trigger currently skips any waits, true if the specified trigger currently "sleeps" or "pauses" when it runs into a Wait action. |