createDialog: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "<dl class="command_description"> <dd class="notedate">" to "<dl class="command_description"> <dt></dt> <dd class="notedate">") |
Lou Montana (talk | contribs) m (Text replacement - " <!-- (DIS)?CONTINUE Notes -->" to "") |
||
| Line 31: | Line 31: | ||
{{GameCategory|tkoh|Scripting Commands}} | {{GameCategory|tkoh|Scripting Commands}} | ||
<dl class="command_description"> | <dl class="command_description"> | ||
<dt></dt> | <dt></dt> | ||
| Line 39: | Line 38: | ||
</dd> | </dd> | ||
</dl> | </dl> | ||
Revision as of 00:51, 6 April 2021
Description
- Description:
- Description needed
- Groups:
- GUI Control
Syntax
- Syntax:
- Syntax needed
- Parameters:
- dialogName: String - class name used in the description.ext / resource.cpp
- Return Value:
- Return value needed
Examples
- Example 1:
_ok = createDialog "RscDisplayGame"; if (!_ok) then {hint "Dialog couldn't be opened!"};
Additional Information
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 29, 2017 - 09:04 (UTC)
- Killzone Kid
- A user dialog created with createDisplay over mission display (findDisplay 46) will stop display event handlers added to mission display from firing. However if it is created with createDialog then the event handlers continue to work.