allVariables: Difference between revisions
Jump to navigation
Jump to search
m (template:command argument fix) |
m (template:command argument fix) |
||
Line 15: | Line 15: | ||
* [[Task]] | * [[Task]] | ||
* [[Location]] | * [[Location]] | ||
|= | |DESCRIPTION= | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| '''allVariables''' namespace |= | | '''allVariables''' namespace |SYNTAX= | ||
| p1= namespace: [[Control]], [[Team Member]], [[Namespace]], [[Object]], [[Group]], [[Task]], [[Location]] |= | | p1= namespace: [[Control]], [[Team Member]], [[Namespace]], [[Object]], [[Group]], [[Task]], [[Location]] |= |
Revision as of 11:25, 7 April 2019
Description
- Description:
- Returns a list of all variables from desired namespace. Namespaces supported:
- Groups:
- Uncategorised
Syntax
- Syntax:
- allVariables namespace
- Parameters:
- namespace: Control, Team Member, Namespace, Object, Group, Task, Location
- Return Value:
- Array of Strings - array of variable names. All names are in lower case (see toLower)
Examples
- Example 1:
_allVarsUINamespace = allVariables uiNamespace;
- Example 2:
_allVarsTrigger = allVariables trigger1;
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 June 11, 2016 - 00:27 (UTC)
- Benargee
- Using profileNamespace and uiNamespace with this command has been disabled in multiplayer. [1]
- Posted on October 1, 2016 - 23:54 (UTC)
- longbow
- One still can use allVariables in Multiplayer against profileNamespace and uiNamespace using config parser. In Description.ext
_EXEC(somevar = allVariables profileNamespace)
in code_allprofilevars = parsingNamespace getVariable "somevar"
but list will be valid only at the moment of parsing config.