parsingNamespace: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "\[\[Category:[ _]?Scripting[ _]Commands[ _]Take[ _]On[ _]Helicopters(\|.*)?\]\]" to "{{GameCategory|tkoh|Scripting Commands}}") |
Lou Montana (talk | contribs) m (Text replacement - "_{10,} " to "") |
||
| Line 1: | Line 1: | ||
{{Command|Comments= | {{Command|Comments= | ||
| arma2 |Game name= | | arma2 |Game name= | ||
| Line 7: | Line 6: | ||
|gr1= Variables |GROUP1= | |gr1= Variables |GROUP1= | ||
| Returns the global namespace attached to config parser. |DESCRIPTION= | | Returns the global namespace attached to config parser. |DESCRIPTION= | ||
| '''parsingNamespace''' |SYNTAX= | | '''parsingNamespace''' |SYNTAX= | ||
| Line 26: | Line 23: | ||
_profVar1 = '''parsingNamespace''' [[getVariable]] "var1";</code>|EXAMPLE1= | _profVar1 = '''parsingNamespace''' [[getVariable]] "var1";</code>|EXAMPLE1= | ||
| [[missionNamespace]], [[uiNamespace]], [[currentNamespace]], [[profileNamespace]], [[localNamespace]], [[allVariables]], [[with]], [[ArmA:_Editing#Forward_Compatibility|Forward Compatibility]] |SEEALSO= | | [[missionNamespace]], [[uiNamespace]], [[currentNamespace]], [[profileNamespace]], [[localNamespace]], [[allVariables]], [[with]], [[ArmA:_Editing#Forward_Compatibility|Forward Compatibility]] |SEEALSO= | ||
| |MPBEHAVIOUR= | | |MPBEHAVIOUR= | ||
}} | }} | ||
Revision as of 02:12, 17 January 2021
Description
- Description:
- Returns the global namespace attached to config parser.
- Groups:
- Variables
Syntax
- Syntax:
- parsingNamespace
- Return Value:
- Namespace
Examples
- Example 1:
parsingNamespace setVariable ["var1",101.23124]; _profVar1 = parsingNamespace getVariable "var1";
Additional Information
- See also:
- missionNamespaceuiNamespacecurrentNamespaceprofileNamespacelocalNamespaceallVariableswithForward Compatibility
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 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()