triggerTimeoutCurrent: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
mNo edit summary
m (Text replacement - "<dt class="note">'''\[\[.*\]\]'''" to "<dt class="note">$1")
Line 35: Line 35:
<!-- Note Section BEGIN -->
<!-- Note Section BEGIN -->
<dd class="notedate">Posted on November 26, 2013
<dd class="notedate">Posted on November 26, 2013
<dt class="note">'''[[User:Killzone_Kid|Killzone_Kid]]'''
<dt class="note">[[]]
<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.

Revision as of 18:11, 19 May 2020

Hover & click on the images for description

Description

Description:
Returns current timeout of the given trigger or -1 if countdown is not in progress.

The trigger could be local or remote but the result returned by this command will be for the current trigger timeout local to the client that executed the command. See createTrigger for more info.
Groups:
Uncategorised

Syntax

Syntax:
triggerTimeoutCurrent trigger
Parameters:
trigger: Object - trigger object
Return Value:
Number - time remaining before trigger activation.

Examples

Example 1:
_remaining = triggerTimeoutCurrent _trigger;

Additional Information

See also:
triggerTimeoutsetTriggerTimeoutwaypointTimeoutCurrent

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

Notes

Posted on November 26, 2013
[[]]
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.

Bottom Section