findDisplay: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (removed note with very incomplete tutorial from 2010)
m (Text replacement - "[] spawn" to "0 spawn")
 
(59 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{Command
{{RV|type=command


| arma1
|game1= arma1
|version1= 1.00


|1.00
|game2= arma2
|version2= 1.00
 
|game3= arma2oa
|version3= 1.50
 
|game4= tkoh
|version4= 1.00
 
|game5= arma3
|version5= 0.50


|gr1= GUI Control
|gr1= GUI Control


| Finds a display by its IDD which can either be defined in [[missionConfigFile]] ([[description.ext]]) or [[configFile]] ([[config.cpp]])<br>
|descr= Finds a display by its IDD which can either be defined in [[missionConfigFile]] ([[Description.ext|description.ext]]) or [[configFile]] ([[config.cpp]]) or by its [[Procedural Textures#UI On Texture|UI On Texture]]'s unique name (see [[displayUniqueName]]).<br>
If the specified display can't be found [[displayNull]] ("No display") is returned, which can be tested with the [[isNull]] command.<br><br>
If the specified display cannot be found, [[displayNull]] is returned.
{{Feature|important|
Dedicated servers and [[Arma 3: Headless Client|headless clients]] do not have a primary display (e.g <sqf inline>findDisplay 46</sqf> will return [[displayNull]]).<br>
Detect both with the [[hasInterface]] command.
}}
 
{{Feature|informative|For a list of (almost) all {{arma3}}'s IDDs, see [[Arma 3: IDD List]].}}
 
|s1= [[findDisplay]] idd
 
|p1= idd: [[Number]]


{{ Important | Dedicated servers and [[Arma 3 Headless Client|headless clients]] don't have a primary display (e.g {{Inline code|findDisplay 46}} will return [[displayNull]]).<br>
|r1= [[Display]]
Detect both with the [[hasInterface]] command. }}


A list of common displays can be found in the notes below; for a full list, see [[findDisplay/Arma 3 IDD list]].
|s2= [[findDisplay]] displayName


| [[findDisplay]] idd
|s2since= arma3 2.12


|p1= idd: [[Number]]
|p21= displayName: [[String]]


| [[Display]]
|r2= [[Display]]


|x1= <code>[] [[spawn]]
|x1= <sqf>
0 spawn
{
{
[[waitUntil]] { ![[isNull]] [[findDisplay]] 46 };
waitUntil { !isNull findDisplay 46 };
[[hint]] "Mission Display is now available!";
hint "Mission Display is now available!";
};</code>
};
|x2= <code>_display = [[findDisplay]] 1;</code>
</sqf>
 
|x2= <sqf>_display = findDisplay 1;</sqf>


| [[allDisplays]], [[displayCtrl]], [[createDisplay]], [[createDialog]], [[dialog]], [[displayNull]], [[controlNull]], [[isNull]], [[createDisplay]], [[ctrlCreate]], [[displayParent]]
|x3= <sqf>private _display = findDisplay "RscDisplayRenderTest";</sqf>
 
|seealso= [[allDisplays]] [[displayCtrl]] [[createDisplay]] [[createDialog]] [[dialog]] [[displayNull]] [[controlNull]] [[isNull]] [[createDisplay]] [[ctrlCreate]] [[displayParent]] [[displayUniqueName]]
}}
}}


<dl class="command_description">
{{Note
<!-- Note Section BEGIN -->
|user= Lou Montana
|timestamp= 20190707122000
|text= Common IDDs:
* 46: Mission display
* 312: Zeus display
* 49: Pause menu
* 602: Inventory
* 24: Chat box
* 300: Weapon state
* 12: Map
* 160: UAV Terminal
}}


<dd class="notedate">Posted on July 07, 2019 - 12:20 (UTC)</dd>
{{Note
<dt class="note">[[User:Lou Montana|Lou Montana]]</dt>
|user= Kronzky
<dd class="note">
|timestamp= 20090615191000
{|class="wikitable sortable"
|text= [[findDisplay]] does ''not'' find displays defined under RscTitles (even when they are visible).<br>
|+ Common IDDs
To access those types of displays, either assign the resource to a global variable, or pass its [[Magic Variables#this_2|this]] value to a script, during the onLoad event:
! Display
e.g. <syntaxhighlight lang="cpp">
! IDD
class RscTitles
|-
{
| Mission display
class MyRsc
| 46
{
|-
onLoad = "myDisplay = (_this select 0)";
| Zeus display
// or
| 312
// onLoad = "_this execVM 'myDialog.sqf'";
|-
// ...
| Pause menu
};
| 49
};
|-
| Inventory
| 602
|-
| Chat box
| 24
|-
| Weapon state
| 300
|-
| Map
| 12
|-
| UAV Terminal
| 160
|}
For a full list, see [[findDisplay/Arma 3 IDD list]].
 
<dd class="notedate">Posted on 15 June 2008
<dt class="note>[[User:Kronzky|Kronzky]]
<dd class="note">
findDisplay does ''not'' find displays defined under RscTitles (even when they are visible).<br>
To access those types of displays, either assign the resource to a global variable, or pass its [[this]] value to a script, during the onLoad event:
e.g. <syntaxhighlight lang="cpp">class RscTitles {
  class MyRsc {
onLoad = "myDisplay = (_this select 0)"; // or
// onLoad = "_this execVM 'myDialog.sqf'";
...
</syntaxhighlight>
</syntaxhighlight>
You can then use the stored value as you would for regular dialogs:
You can then use the stored value as you would for regular dialogs:
<code>(myDisplay [[displayCtrl]] 1111) [[ctrlSetText]] "hello there");</code>
<sqf>(myDisplay displayCtrl 1111) ctrlSetText "hello there");</sqf>
}}


{{Note
|user= Nelis75733126
|timestamp= 20170625093200
|text= I have tested the behavior of this command and I found out that <sqf inline>findDisplay</sqf> appears to only return the display AFTER any {{Link|User_Interface_Event_Handlers#onLoad|onLoad}} event handler of that display is done.<br>
Meaning: using [[findDisplay]] inside the code of an onLoad event handler is useless.
}}


<dd class="notedate">Posted on June 25, 2017 - 09:32 (UTC)
{{Note
<dt class="note">[[User:IT07|IT07]]
|user= Demellion
<dd class="note">
|timestamp= 20170814122200
I have tested the behavior of this command and I found out that it [ findDisplay ] appears to only return the display AFTER any onLoad event handler of that display is done. So, using findDisplay inside an onLoad event handler is useless.
|text= There are some specific cases, where [[findDisplay]] will not be able to find an existing display. Here's the cases and how to act on them:<br>
 
<syntaxhighlight lang="cpp">
<dd class="notedate">Posted on August 14, 2017 - 12:22 (UTC)
// Your display has IDD= -1.
<dt class="note">[[User:Demellion|Demellion]]
<dd class="note">
There are some specific cases, where '''findDisplay''' will not be able to find an existing display. Here's the cases and how to act on them:<br>
<syntaxhighlight lang="cpp">// Your display has IDD= -1.
class RscDisplayNew
class RscDisplayNew
{
{
idd = -1;
idd = -1;
scriptName = "RscDisplayNew";
scriptName = "RscDisplayNew";
...
// ...
};</syntaxhighlight>
};
<syntaxhighlight lang="cpp">// Your display doesn't have IDD
</syntaxhighlight>
<syntaxhighlight lang="cpp">
// Your display doesn't have IDD
class RscDisplayNew
class RscDisplayNew
{
{
scriptName = "RscDisplayNew";
scriptName = "RscDisplayNew";
...
// ...
};</syntaxhighlight>
};
<syntaxhighlight lang="cpp">// Your display doesn't have scriptname with IDD = -1
</syntaxhighlight>
<syntaxhighlight lang="cpp">
// Your display doesn't have scriptname with IDD = -1
class RscDisplayNew
class RscDisplayNew
{
{
idd = -1;
idd = -1;
...
// ...
};</syntaxhighlight>
};
<syntaxhighlight lang="cpp">// Your display doesn't have scriptname, neither IDD
</syntaxhighlight>
<syntaxhighlight lang="cpp">
// Your display doesn't have scriptname, neither IDD
class RscDisplayNew
class RscDisplayNew
{
{
...
// ...
};</syntaxhighlight>
};
</syntaxhighlight>


# You actually can find a -1 display, but this means finding a display with this IDD might be a problem, when there are a few displays marked as -1.<!--
# You actually can find a -1 display, but this means finding a display with this IDD might be a problem, when there are a few displays marked as -1.<!--
-->So as you can see, theres an entry called '''scriptName'''. You can get a reference to this display by using [[uiNamespace]]:<!--
-->So as you can see, theres an entry called '''scriptName'''. You can get a reference to this display by using [[uiNamespace]]:<!--
--><code>(uiNamespace getVariable "RscDisplayNew")</code><!--
--><sqf>(uiNamespace getVariable "RscDisplayNew")</sqf><!--
-->'''NOTE''': Variables are overwritten with a reference of the last declared display under the same scriptName entry. Take a look at case 3 for solution.
-->'''NOTE''': Variables are overwritten with a reference of the last declared display under the same scriptName entry. Take a look at case 3 for solution.
# Displays without IDD's can actually exist. They can be manipulated only in a way described in the first case using [[uiNamespace]].
# Displays without IDDs can actually exist. They can be manipulated only in a way described in the first case using [[uiNamespace]].
# You can really have this display seeking it manually in a [[allDisplays]] return. This is experimental, but working option.
# You can really have this display seeking it manually in a [[allDisplays]] return. This is experimental, but working option.
# You will have a problem finding this display, since this display doesn't exist even in [[allDisplays]](?) return. Behaviour unknown.
# You will have a problem finding this display, since this display doesn't exist even in [[allDisplays]](?) return. Behaviour unknown.
</dd>
}}
</dl>


<!-- Note Section END -->
{{Note
</dl>
|user= AVespade
|timestamp= 20230507025558
|text= Since findDisplay is case-sensitive, and any [[Procedural_Textures#UI_On_Texture|UI On Texture]] unique names defined inside a p3d file will always be forced to lowercase, the unique name you search for with findDisplay will need to be lowercase.


<sqf>private _display = findDisplay "rscdisplayrendertest";</sqf>


[[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]]
Use of [[toLower]] may be useful to improve legibility or flow, especially in cases where a UI On Texture's unique name is the same as the class name.
{{GameCategory|arma1|Scripting Commands}}
<sqf>private _display = findDisplay (toLower "RscDisplayRenderTest");</sqf>
{{GameCategory|arma2|Scripting Commands}}
}}
{{GameCategory|tkoh|Scripting Commands}}
{{GameCategory|arma3|Scripting Commands}}

Latest revision as of 21:24, 2 September 2024

Hover & click on the images for description

Description

Description:
Finds a display by its IDD which can either be defined in missionConfigFile (description.ext) or configFile (config.cpp) or by its UI On Texture's unique name (see displayUniqueName).
If the specified display cannot be found, displayNull is returned.
Dedicated servers and headless clients do not have a primary display (e.g findDisplay 46 will return displayNull).
Detect both with the hasInterface command.
For a list of (almost) all Arma 3's IDDs, see Arma 3: IDD List.
Groups:
GUI Control

Syntax

Syntax:
findDisplay idd
Parameters:
idd: Number
Return Value:
Display

Alternative Syntax

Syntax:
findDisplay displayName
Parameters:
displayName: String
Return Value:
Display

Examples

Example 1:
0 spawn { waitUntil { !isNull findDisplay 46 }; hint "Mission Display is now available!"; };
Example 2:
_display = findDisplay 1;
Example 3:
private _display = findDisplay "RscDisplayRenderTest";

Additional Information

See also:
allDisplays displayCtrl createDisplay createDialog dialog displayNull controlNull isNull createDisplay ctrlCreate displayParent displayUniqueName

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
Lou Montana - c
Posted on Jul 07, 2019 - 12:20 (UTC)
Common IDDs:
  • 46: Mission display
  • 312: Zeus display
  • 49: Pause menu
  • 602: Inventory
  • 24: Chat box
  • 300: Weapon state
  • 12: Map
  • 160: UAV Terminal
Kronzky - c
Posted on Jun 15, 2009 - 19:10 (UTC)
findDisplay does not find displays defined under RscTitles (even when they are visible).
To access those types of displays, either assign the resource to a global variable, or pass its this value to a script, during the onLoad event: e.g.
class RscTitles
{
	class MyRsc
	{
		onLoad = "myDisplay = (_this select 0)";
		// or
		// onLoad = "_this execVM 'myDialog.sqf'";
		// ...
	};
};

You can then use the stored value as you would for regular dialogs:

(myDisplay displayCtrl 1111) ctrlSetText "hello there");

Nelis75733126 - c
Posted on Jun 25, 2017 - 09:32 (UTC)
I have tested the behavior of this command and I found out that findDisplay appears to only return the display AFTER any onLoad event handler of that display is done.
Meaning: using findDisplay inside the code of an onLoad event handler is useless.
Demellion - c
Posted on Aug 14, 2017 - 12:22 (UTC)
There are some specific cases, where findDisplay will not be able to find an existing display. Here's the cases and how to act on them:
// Your display has IDD= -1.
class RscDisplayNew
{
	idd = -1;
	scriptName = "RscDisplayNew";
	// ...
};
// Your display doesn't have IDD
class RscDisplayNew
{
	scriptName = "RscDisplayNew";
	// ...
};
// Your display doesn't have scriptname with IDD = -1
class RscDisplayNew
{
	idd = -1;
	// ...
};
// Your display doesn't have scriptname, neither IDD
class RscDisplayNew
{
	// ...
};
  1. You actually can find a -1 display, but this means finding a display with this IDD might be a problem, when there are a few displays marked as -1.So as you can see, theres an entry called scriptName. You can get a reference to this display by using uiNamespace:
    (uiNamespace getVariable "RscDisplayNew")
    NOTE: Variables are overwritten with a reference of the last declared display under the same scriptName entry. Take a look at case 3 for solution.
  2. Displays without IDDs can actually exist. They can be manipulated only in a way described in the first case using uiNamespace.
  3. You can really have this display seeking it manually in a allDisplays return. This is experimental, but working option.
  4. You will have a problem finding this display, since this display doesn't exist even in allDisplays(?) return. Behaviour unknown.
AVespade - c
Posted on May 07, 2023 - 02:55 (UTC)
Since findDisplay is case-sensitive, and any UI On Texture unique names defined inside a p3d file will always be forced to lowercase, the unique name you search for with findDisplay will need to be lowercase.
private _display = findDisplay "rscdisplayrendertest";
Use of toLower may be useful to improve legibility or flow, especially in cases where a UI On Texture's unique name is the same as the class name.
private _display = findDisplay (toLower "RscDisplayRenderTest");