triggerTimeoutCurrent: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "<dl class="command_description"> <dd class="notedate">" to "<dl class="command_description"> <dt></dt> <dd class="notedate">") |
Lou Montana (talk | contribs) m (Text replacement - " +" to " ") |
||
| Line 30: | Line 30: | ||
<dd class="note"> | <dd class="note"> | ||
Triggers have their own schedule. If you create a trigger with timeout and try to read [[triggerTimeoutCurrent]] immediately it will return -1. This is because the countdown will not start until the next scheduled trigger check is due, and this could take up to 0.5 seconds. | Triggers have their own schedule. If you create a trigger with timeout and try to read [[triggerTimeoutCurrent]] immediately it will return -1. This is because the countdown will not start until the next scheduled trigger check is due, and this could take up to 0.5 seconds. | ||
</dl> | </dl> | ||
Revision as of 09:29, 11 June 2021
Description
- Description:
- Description needed
- Groups:
- Triggers
Syntax
- Syntax:
- Syntax needed
- Parameters:
- trigger: Object - trigger object
- Return Value:
- Return value needed
Examples
- Example 1:
private _remaining = triggerTimeoutCurrent _trigger;
Additional Information
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note
- Posted on November 26, 2013
- Killzone_Kid
- Triggers have their own schedule. If you create a trigger with timeout and try to read triggerTimeoutCurrent immediately it will return -1. This is because the countdown will not start until the next scheduled trigger check is due, and this could take up to 0.5 seconds.