ctrlEnable: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "</dd> </dl>" to "</dd> </dl>") |
Lou Montana (talk | contribs) m (Some wiki formatting) |
||
Line 28: | Line 28: | ||
|gr1= GUI Control | |gr1= GUI Control | ||
|descr= Enables or disables 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. | |descr= Enables or disables 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. | |||
|s1= | |s1= [[ctrlEnable]] [idc, enable] | ||
|p1= idc: [[Number]] - Control IDC | |p1= idc: [[Number]] - Control IDC | ||
|p2= enable: [[Boolean]] - [[true | |p2= enable: [[Boolean]] - [[true]] to enable the control, [[false]] to disable it | ||
|r1= [[Nothing]] | |r1= [[Nothing]] | ||
|s2= controlName [[ctrlEnable]] | |s2= controlName [[ctrlEnable]] enable | ||
|p21= | |p21= controlName: [[Control]] | ||
|p22= enable: [[Boolean]] | |p22= enable: [[Boolean]] | ||
Line 62: | Line 64: | ||
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> | ||
<dt></dt> | <dt></dt> | ||
<dd class="notedate">Posted on September 7, 2020 - 22:26 (UTC)</dd> | <dd class="notedate">Posted on September 7, 2020 - 22:26 (UTC)</dd> | ||
Line 70: | Line 73: | ||
<code>class MyDialog | <code>class MyDialog | ||
{ | { | ||
class MyControl | |||
{ | |||
[[User_Interface_Event_Handlers#onLoad|onLoad]] = "([[Magic Variables#this|_this]] [[#]] 0) [[ctrlEnable]] [[false]];"; | |||
}; | |||
};</code> | };</code> | ||
</dd> | </dd> | ||
</dl> | </dl> |
Revision as of 14:45, 19 June 2021
Description
- Description:
- Enables or disables 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:
- GUI Control
Syntax
- Syntax:
- ctrlEnable [idc, enable]
- Parameters:
- idc: Number - Control IDC
- 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
- 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;"; }; };
Categories:
- Scripting Commands
- Introduced with Operation Flashpoint version 1.75
- Operation Flashpoint: New Scripting Commands
- Operation Flashpoint: Scripting Commands
- Operation Flashpoint: Elite: Scripting Commands
- ArmA: Armed Assault: Scripting Commands
- Arma 2: Scripting Commands
- Arma 2: Operation Arrowhead: Scripting Commands
- Take On Helicopters: Scripting Commands
- Arma 3: Scripting Commands
- Command Group: GUI Control
- Scripting Commands: Local Effect