ctrlEnable: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "Dialog Control" to "Arma: GUI Configuration") |
Lou Montana (talk | contribs) m (Text replacement - "<br />" to "<br>") |
||
Line 68: | Line 68: | ||
<dt class="note">[[User:Yuval|Yuval]]</dt> | <dt class="note">[[User:Yuval|Yuval]]</dt> | ||
<dd class="note"> | <dd class="note"> | ||
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.<br | 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.<br> | ||
As a general rule of thumb, enabled controls should only be already on the top of the GUI. | As a general rule of thumb, enabled controls should only be already on the top of the GUI. | ||
</dd> | </dd> | ||
</dl> | </dl> | ||
<!-- DISCONTINUE Notes --> | <!-- DISCONTINUE Notes --> |
Revision as of 10:40, 19 March 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
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 ArmA
- Command Group: GUI Control
- Scripting Commands Arma 2
- Scripting Commands Arma 3
- Scripting Commands Take On Helicopters