parsingNamespace: 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 26: | Line 26: | ||
| [[missionNamespace]], [[uiNamespace]], [[currentNamespace]], [[profileNamespace]], [[localNamespace]], [[allVariables]], [[with]], [[ArmA:_Editing#Forward_Compatibility|Forward Compatibility]] | | [[missionNamespace]], [[uiNamespace]], [[currentNamespace]], [[profileNamespace]], [[localNamespace]], [[allVariables]], [[with]], [[ArmA:_Editing#Forward_Compatibility|Forward Compatibility]] | ||
}} | }} | ||
{{GameCategory|arma2|Scripting Commands}} | {{GameCategory|arma2|Scripting Commands}} | ||
Revision as of 23:39, 10 June 2021
Description
- Description:
- Description needed
- Groups:
- Variables
Syntax
- Syntax:
- Syntax needed
- Return Value:
- Namespace
Examples
- Example 1:
parsingNamespace setVariable ["var1",101.23124]; _profVar1 = parsingNamespace getVariable "var1";
Additional Information
- See also:
- See also needed
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 January 27, 2015 - 18:08 (UTC)
- BrotherhoodOfHam
Any global variable defined in a config using __EXEC() will be stored in this namespace.
For example in the description.ext:
__EXEC(testVar = 1);The variable "testVar" can be accessed during mission run time using getVariablehint str (parsingNamespace getVariable ["testVar", 0]);The above example would print 1.
This example however:__EXEC(_testVar = 1);Would print 0, because adding an underscore will make the variable local to the config in the same way that it would make it local to a script.
See PreProcessor Commands for more details on __EXEC()