createDialog: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (Text replacement - "|Game version=" to "|Game version= |gr1= GUI Control |GROUP1= ") |
||
Line 5: | Line 5: | ||
|1.5|Game version= | |1.5|Game version= | ||
|gr1= GUI Control |GROUP1= | |||
|eff= local |Multiplayer Effects= | |eff= local |Multiplayer Effects= |
Revision as of 10:04, 18 September 2020
Description
- Description:
- Create a dialog which is defined either in the mission's description.ext, in the campaign's description.ext or in the global resource.cpp. The given name has to be the class name used in one of these files. If another dialog is already opened, the desired dialog is created as a child dialog of the one already opened.
- Groups:
- GUI Control
Syntax
- Syntax:
- createDialog dialogName
- Parameters:
- dialogName: String - class name used in the description.ext / resource.cpp
- Return Value:
- Boolean - true when the dialog was created successfully
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
Notes
Bottom Section
- 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.
Categories:
- Scripting Commands
- Introduced with Operation Flashpoint version 1.5
- Operation Flashpoint: New Scripting Commands
- Operation Flashpoint: Scripting Commands
- Command Group: GUI Control
- Scripting Commands: Local Effect
- Scripting Commands OFP 1.99
- Scripting Commands OFP 1.96
- Scripting Commands Armed Assault
- Scripting Commands Arma 2
- Scripting Commands Arma 3
- Scripting Commands Take On Helicopters