ctrlEnable: Difference between revisions
Jump to navigation
Jump to search
m (Text replacement - "\[\[[cC]ategory:[sS]cripting [cC]ommands\|[a-z A-Z 0-9_]+\]\]" to "") |
Lou Montana (talk | contribs) m (Text replacement - "\| *((\[\[[a-zA-Z0-9_ |()]+\]\],? ?)+) * \}\}" to "|seealso= $1 }}") |
||
Line 37: | Line 37: | ||
|x2= <code>_ctrl [[ctrlEnable]] [[false]]</code> | |x2= <code>_ctrl [[ctrlEnable]] [[false]]</code> | ||
| [[ctrlEnabled]] | |seealso= [[ctrlEnabled]] | ||
}} | }} | ||
Revision as of 23:28, 16 February 2021
Description
- Description:
- Description needed
- Groups:
- GUI Control
Syntax
- Syntax:
- Syntax needed
- Parameters:
- [idc, enable]: Array
- idc: Number - control ID
- enable: Boolean - true to enable the control, false to disable it
- Return Value:
- Return value needed
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
- 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.
- Posted on September 7, 2020 - 22:26 (UTC)
- R3vo
-
One can disable a control when it is loaded by using ctrlEnable in the onLoad event handler.
class MyDialog { class MyControl { onLoad = "(_this # 0) ctrlEnable false;"; }; };