createDisplay: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
Line 5: | Line 5: | ||
|1.00|Game version= | |1.00|Game version= | ||
|gr1= GUI Control |=GROUP1 | |||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
Revision as of 10:13, 16 September 2020
Description
- Description:
- Creates child display of given display and loads from "resourceName". The notable difference between createDisplay and createDialog is that with createDisplay the player would be able to move whilst having control of the mouse pointer.
Since Arma 3 v1.49.131653 createDisplay returns Display and will first look in description.ext for resourceName config, if not found, it will then look in main config.
Displays created with both createDisplay and createDialog will take control of the mouse pointer and will close when user presses Esc._emptyDisplay = findDisplay 46 createDisplay "RscDisplayEmpty";
If display is needed which exists independently, it can be created in IGUI layer with cutRsc command."someLayer" cutRsc ["RscTitleDisplayEmpty", "PLAIN"]; _emptyDisplay = uiNamespace getVariable "RscTitleDisplayEmpty";
Such display can be closed with closeDisplay command or by overwriting the same cut layer with another output. Note that "Unload" EH for some reason does not work with such display. - Groups:
- GUI Control
Syntax
- Syntax:
- parent createDisplay resourceName
- Parameters:
- parent: Display
- resourceName: String - custom display class defined in description.ext or existing display class from main config
- Return Value:
- Nothing or (Since Arma 3 v1.49.131653) Display
Examples
- Example 1:
findDisplay 46 createDisplay "RscCredits";
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 August 23, 2014 - 23:36 (UTC)
- Killzone Kid
-
Do not simply createDisplay from UI context code such as "ButtonDown" UI Event handler, as it will crash the game. Instead use spawn scope:
[] spawn {findDisplay 46 createDisplay "RscCredits"};
- Posted on November 15, 2014 - 13:20 (UTC)
- MrPineapple
-
Arma3 v1.34
When using CreateDisplay instead of CreateDialog, all the commands for working with the controls of the display only work with the control version, not the IDC version.
EXAMPLE:LbAdd [1234, "item"]; // does not work on displays, and won't error either _ctrl LbAdd "item"; // does work with displays
So you have to use the control(DisplayCtrl) and not the IDC.
- Posted on July 29, 2017 - 09:02 (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.
- Posted on June 21, 2020 - 17:01 (UTC)
- Target_practice
- Creating a display with the same parent as an existing display will destroy the latter and all of its children. However, their onUnload, onChildDestroyed, and onDestroy event handlers will not fire.