ctrlEnable: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "[[Category:Scripting Commands ArmA|" to "[[Category:Scripting Commands Armed Assault|") |
m (formatting and example 3) |
||
Line 36: | Line 36: | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
|x1= < | |x1= <code>[[ctrlEnable]] [100, [[false]]]</code> |EXAMPLE1= | ||
|x2= <code>_ctrl ctrlEnable [[false]]</code> |EXAMPLE2= | |x2= <code>_ctrl [[ctrlEnable]] [[false]]</code> |EXAMPLE2= | ||
|x3= <code>onLoad = "([[_this]] [[#]] 0) [[ctrlEnable]] [[false]];";{{cc|A control can be disabled when it's loaded by using [[ctrlEnable]] in the [[User_Interface_Event_Handlers#onLoad|onLoad]] event handler.}}</code> |EXAMPLE3= | |||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
Revision as of 15:43, 7 September 2020
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
- Example 3:
onLoad = "(_this # 0) ctrlEnable false;";// A control can be disabled when it's loaded by using ctrlEnable in the onLoad event handler.
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.
Categories:
- Scripting Commands
- Introduced with Operation Flashpoint version 1.5
- Operation Flashpoint: New Scripting Commands
- Operation Flashpoint: Scripting Commands
- Command Group: Uncategorised
- Scripting Commands: Local Effect
- Scripting Commands OFP 1.99
- Scripting Commands OFP 1.96
- Scripting Commands Armed Assault
- Command Group: GUI Control
- Scripting Commands Arma 2
- Scripting Commands Arma 3
- Scripting Commands Take On Helicopters