createDisplay: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "v1\.49\.[0-9]{6}" to "v1.50")
m (Text replacement - "<sqf>([^↵][^<]*↵[^<]*)<\/sqf>" to "<sqf> $1 </sqf>")
 
(35 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{RV|type=command
{{RV|type=command


| arma1
|game1= arma1
|version1= 1.00


|1.00
|game2= arma2
|version2= 1.00


|gr1= GUI Control
|game3= arma2oa
|version3= 1.50


| 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 around while the display is shown.<br>
|game4= tkoh
Displays created with [[createDisplay]] or [[createDialog]] will take control of the mouse pointer and will close when user presses <tt>Escape</tt>.
|version4= 1.00
{{Feature|arma3 | Since {{arma3}} v1.50 [[createDisplay]] returns [[Display]] and will first look in ''description.ext'' for resourceName config, if not found, it will then look in main config.}}
{{Feature | Informative | If an ''overlay'' is needed instead, use [[cutRsc]].}}


| parent '''createDisplay''' resourceName
|game5= arma3
|version5= 0.50


|p1= parent: [[Display]]
|gr1= GUI Control


|p2= resourceName: [[String]] - custom display class defined in [[description.ext]] or existing display class from main config
|descr= 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 around while the display is shown.<br>
Displays created with [[createDisplay]] or [[createDialog]] will take control of the mouse pointer and will close when user presses {{Controls|Esc}}.
{{Feature|arma3|Since {{arma3}} v1.50 [[createDisplay]] returns [[Display]] and will first look in [[Description.ext|description.ext]] for resourceName config, if not found, it will then look in main config.}}
{{Feature|informative|If an ''overlay'' is needed instead, use [[cutRsc]].}}


| [[Display]] (since {{arma3}} v1.50, [[Nothing]] before)
|s1= parent [[createDisplay]] resourceName
 
|x1= <code>[[findDisplay]] 46 [[createDisplay]] "RscCredits";</code>


|x2= <code>{{cc|creates an empty display}}
|p1= parent: [[Display]]
[[private]] _emptyDisplay {{=}} [[findDisplay]] 46 [[createDisplay]] "RscDisplayEmpty";</code>


|seealso= [[closeDisplay]], [[createDialog]], [[displayCtrl]], [[dialog]], [[displayNull]], [[controlNull]], [[ctrlCreate]], [[displayParent]]
|p2= resourceName: [[String]] - custom display class defined in [[Description.ext|description.ext]] or existing display class from main config
}}


|r1= [[Display]] (since {{GVI|arma3|1.50|size= 0.75}}, [[Nothing]] before)


|x1= <sqf>findDisplay 46 createDisplay "RscCredits";</sqf>


{{GameCategory|arma1|Scripting Commands}}
|x2= <sqf>
{{GameCategory|arma2|Scripting Commands}}
// creates an empty display
{{GameCategory|arma3|Scripting Commands}}
private _emptyDisplay = findDisplay 46 createDisplay "RscDisplayEmpty";
{{GameCategory|tkoh|Scripting Commands}}
</sqf>


<!-- CONTINUE Notes -->
|seealso= [[closeDisplay]] [[createDialog]] [[displayCtrl]] [[dialog]] [[displayNull]] [[controlNull]] [[ctrlCreate]] [[displayParent]]
<dl class="command_description">
}}
<dd class="notedate">Posted on August 23, 2014 - 23:36 (UTC)</dd>
<dt class="note">[[User:Killzone Kid|Killzone Kid]]</dt>
<dd class="note">
Do not simply [[createDisplay]] from UI context code such as "ButtonDown" UI Event handler, as it will crash the game. Instead use [[spawn]] scope:
<code>[] [[spawn]] {[[findDisplay]] 46 [[createDisplay]] "RscCredits"};</code>
</dd>


<dd class="notedate">Posted on November 15, 2014 - 13:20 (UTC)</dd>
{{Note
<dt class="note">[[User:MrPineapple|MrPineapple]]</dt>
|user= MrPineapple
<dd class="note">
|timestamp= 20141115132000
{{arma3}} v1.34<br>
|text= 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:
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:
<sqf>
<code>LbAdd [1234, "item"]; {{cc|does not work on displays, and won't error either}}
lbAdd [1234, "item"]; // does not work on displays, and won't error either
_ctrl LbAdd "item"; {{cc|does work with displays}}</code>
_ctrl lbAdd "item"; // does work with displays
</sqf>
So you have to use the control(DisplayCtrl) and not the IDC.
So you have to use the control(DisplayCtrl) and not the IDC.
|game= arma3
|version= 1.34
}}


</dd>
{{Note
|user= Killzone_Kid
|timestamp= 20170629090200
|text= A user dialog created with [[createDisplay]] over mission display ([[findDisplay]] 46) will stop [[displayAddEventHandler|display event handlers]] added to mission display from firing. However if it is created with [[createDialog]] then the event handlers continue to work.
}}


<dd class="notedate">Posted on July 29, 2017 - 09:02 (UTC)</dd>
{{Note
<dt class="note">[[User:Killzone Kid|Killzone Kid]]</dt>
|user= Target_practice
<dd class="note"> A user dialog created with [[createDisplay]] over mission display ([[findDisplay]] 46) will stop [[displayAddEventHandler|display event handlers]] added to mission display from firing. However if it is created with [[createDialog]] then the event handlers continue to work.
|timestamp= 20200621170100
</dd>
|text= Creating a display with the same parent as an existing display will destroy the latter and all of its children. However, their [[User_Interface_Event_Handlers#onUnload|onUnload]], [[User_Interface_Event_Handlers#onChildDestroyed|onChildDestroyed]], and [[User_Interface_Event_Handlers#onDestroy|onDestroy]] event handlers will not fire.
}}


<dd class="notedate">Posted on June 21, 2020 - 17:01 (UTC)</dd>
{{Note
<dt class="note">[[User:Target_practice|Target_practice]]</dt>
|user= 7erra
<dd class="note">
|timestamp= 20220205154714
Creating a display with the same parent as an existing display will destroy the latter and all of its children. However, their [[User_Interface_Event_Handlers#onUnload|onUnload]], [[User_Interface_Event_Handlers#onChildDestroyed|onChildDestroyed]], and [[User_Interface_Event_Handlers#onDestroy|onDestroy]] event handlers will not fire.
|text= When trying to create a display with [[createDisplay]] on a non existing display the command will fail silently and return [[displayNull]].
</dd>
}}
</dl>
<!-- DISCONTINUE Notes -->

Latest revision as of 19:42, 3 September 2024

Logo A1 black.png1.00Logo A2.png1.00A2 OA Logo.png1.50tkoh logo small.png1.00Arma 3 logo black.png0.50
Hover & click on the images for description

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 around while the display is shown.
Displays created with createDisplay or createDialog will take control of the mouse pointer and will close when user presses Esc.
Arma 3
Since Arma 3 v1.50 createDisplay returns Display and will first look in description.ext for resourceName config, if not found, it will then look in main config.
ⓘ
If an overlay is needed instead, use cutRsc.
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:
Display (since Arma 3 logo black.png1.50, Nothing before)

Examples

Example 1:
findDisplay 46 createDisplay "RscCredits";
Example 2:
// creates an empty display private _emptyDisplay = findDisplay 46 createDisplay "RscDisplayEmpty";

Additional Information

See also:
closeDisplay createDialog displayCtrl dialog displayNull controlNull ctrlCreate displayParent

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
MrPineapple - c
Posted on Nov 15, 2014 - 13:20 (UTC)
Arma 3 logo black.png1.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:

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.

Killzone_Kid - c
Posted on Jun 29, 2017 - 09:02 (UTC)
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.
Target_practice - c
Posted on Jun 21, 2020 - 17:01 (UTC)
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.
7erra - c
Posted on Feb 05, 2022 - 15:47 (UTC)
When trying to create a display with createDisplay on a non existing display the command will fail silently and return displayNull.
Retrieved from "https://community.bistudio.com/wiki?title=createDisplay&oldid=369323"