findDisplay: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\|( *\[\[[a-zA-Z]+\]\]) * \|x1=" to "\|r1=$1 \|x1=") |
Lou Montana (talk | contribs) m (Text replacement - "\|" to "|") |
||
Line 19: | Line 19: | ||
|p1= idd: [[Number]] | |p1= idd: [[Number]] | ||
|r1= [[Display]] | |||
|x1= <code>[] [[spawn]] | |||
{ | { | ||
[[waitUntil]] { ![[isNull]] [[findDisplay]] 46 }; | [[waitUntil]] { ![[isNull]] [[findDisplay]] 46 }; |
Revision as of 10:30, 10 June 2021
Description
- Description:
- Description needed
- Groups:
- GUI Control
Syntax
- Syntax:
- Syntax needed
- Parameters:
- idd: Number
- Return Value:
- Display
Examples
- Example 1:
[] spawn { waitUntil { !isNull findDisplay 46 }; hint "Mission Display is now available!"; };
- Example 2:
_display = findDisplay 1;
Additional Information
- See also:
- allDisplaysdisplayCtrlcreateDisplaycreateDialogdialogdisplayNullcontrolNullisNullcreateDisplayctrlCreatedisplayParent
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 07, 2019 - 12:20 (UTC)
- Lou Montana
-
Common IDDs Display IDD Mission display 46 Zeus display 312 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.
- Posted on 15 June 2008
- Kronzky
-
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");
- Posted on June 25, 2017 - 09:32 (UTC)
- IT07
- 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.
- Posted on August 14, 2017 - 12:22 (UTC)
- Demellion
-
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 { ... };
- 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. - Displays without IDD's 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 will have a problem finding this display, since this display doesn't exist even in allDisplays(?) return. Behaviour unknown.
- 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: