ctrlCommit: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "<dd class="note">([^}]*)<code>([^<]*)<\/code>" to "<dd class="note">$1<sqf>$2</sqf>")
m (Text replacement - "<dd class="note">([^}]*)<code>([^<]*)<\/code>" to "<dd class="note">$1<sqf>$2</sqf>")
Line 52: Line 52:
_ctrl ctrlCommit 1;</sqf>
_ctrl ctrlCommit 1;</sqf>
Will actually result in:
Will actually result in:
<code>'''[60 FPS and higher]''' = ~1.0 seconds
<sqf>'''[60 FPS and higher]''' = ~1.0 seconds
'''[30 FPS and around]''' = ~1.2 seconds
'''[30 FPS and around]''' = ~1.2 seconds
'''[10 FPS and anything lower]''' = ~5-10 seconds
'''[10 FPS and anything lower]''' = ~5-10 seconds
</code>
</sqf>
This phenomenon probably occurs because of engine time simulation disruption caused by performance damage.<br><br>
This phenomenon probably occurs because of engine time simulation disruption caused by performance damage.<br><br>



Revision as of 11:58, 13 May 2022

Hover & click on the images for description

Description

Description:
Commits control animation to last specified duration.
The duration of the animation is not guaranteed to be exactly the same as the given time.
Groups:
GUI Control

Syntax

Syntax:
control ctrlCommit time
Parameters:
control: Control - control to animate
time: Number - animation duration
Return Value:
Nothing

Examples

Example 1:
_control ctrlCommit 2; // make animation last approx. 2 seconds

Additional Information

See also:
ctrlCommittedctrlSetPositionctrlSetFade

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 April 11, 2015 - 23:06 (UTC)
IT07
Use this command if you want to for example change the position or size of a control.
Posted on August 28, 2017 - 11:33 (UTC)
Demellion
The resulting speed might not to be exactly what ctrlCommit commands it to be. It seems to be dependent on your current framerate. Example:
_ctrl ctrlSetFade 0.5; _ctrl ctrlCommit 1;
Will actually result in:
'''[60 FPS and higher]''' = ~1.0 seconds '''[30 FPS and around]''' = ~1.2 seconds '''[10 FPS and anything lower]''' = ~5-10 seconds
This phenomenon probably occurs because of engine time simulation disruption caused by performance damage.

*Original note changed by R3vo (talk) 15:24, 25 January 2021 (CET)