ctrlEnable: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "<br />" to "<br>")
m (Text replacement - "[[Category:Scripting_Commands_Take_On_Helicopters" to "[[Category:Scripting Commands Take On Helicopters")
Line 61: Line 61:
[[Category:Scripting Commands Arma 2|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Arma 2|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands Take On Helicopters|{{uc:{{PAGENAME}}}}]]


<!-- CONTINUE Notes -->
<!-- CONTINUE Notes -->

Revision as of 01:15, 6 April 2020

Hover & click on the images for description

Description

Description:
Enable or disable a control of the currently active user dialog. Disabled controls cannot be clicked onto. Read Arma: GUI Configuration for more information about user dialogs and controls.
Groups:
Uncategorised

Syntax

Syntax:
ctrlEnable [idc, enable]
Parameters:
[idc, enable]: Array
idc: Number - control ID
enable: Boolean - true to enable the control, false to disable it
Return Value:
Nothing

Alternative Syntax

Syntax:
controlName ctrlEnable enable
Parameters:
controlName: Control
enable: Boolean
Return Value:
Nothing

Examples

Example 1:
ctrlEnable [100, false]
Example 2:
_ctrl ctrlEnable false

Additional Information

See also:
ctrlEnabled

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

Bottom Section

Posted on July 20, 2017 - 11:59 (UTC)
Yuval
Please do note that enabled controls can gain focus upon click. Therefore do not enable background controls or else they will cover any controls on top of them.
As a general rule of thumb, enabled controls should only be already on the top of the GUI.