parsingNamespace: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "Category:Scripting Commands ArmA2" to "Category:Scripting Commands Arma 2") |
Lou Montana (talk | contribs) m (Text replacement - "" to "") |
||
| (53 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
{{ | {{RV|type=command | ||
| arma2 | | |game1= arma2 | ||
|version1= 1.00 | |||
|1. | |game2= arma2oa | ||
|version2= 1.50 | |||
| | |game3= tkoh | ||
|version3= 1.00 | |||
| | |game4= arma3 | ||
|version4= 0.50 | |||
| | |gr1= Namespaces | ||
|gr2= Variables | |||
| | |descr= Returns the global namespace attached to config parser. | ||
| | |s1= [[parsingNamespace]] | ||
| [[Namespace]] | |r1= [[Namespace]] | ||
|x1= <sqf> | |||
parsingNamespace setVariable ["var1", 101.23124]; | |||
_profVar1 = parsingNamespace getVariable "var1"; | |||
</sqf> | |||
| | |seealso= [[missionNamespace]] [[uiNamespace]] [[currentNamespace]] [[profileNamespace]] [[localNamespace]] [[allVariables]] [[with]] [[ArmA:_Editing#Forward_Compatibility|Forward Compatibility]] | ||
}} | }} | ||
{{Note | |||
|user= BrotherhoodOfHam | |||
|timestamp= 20150127180800 | |||
|text= Any global variable defined in a config using __EXEC() will be stored in this namespace.<br> | |||
For example in the description.ext:<br> | |||
<sqf>__EXEC(testVar = 1);</sqf> | |||
For example in the description.ext:<br | |||
< | |||
The variable "testVar" can be accessed during mission run time using [[getVariable]] | The variable "testVar" can be accessed during mission run time using [[getVariable]] | ||
< | <sqf>hint str (parsingNamespace getVariable ["testVar", 0]);</sqf> | ||
The above example would print 1.<br | The above example would print 1.<br><br> | ||
This example however: | This example however: | ||
< | <sqf>__EXEC(_testVar = 1);</sqf> | ||
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.<br | 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.<br><br> | ||
See [[PreProcessor Commands]] for more details on __EXEC() | See [[PreProcessor Commands]] for more details on __EXEC() | ||
}} | |||
Latest revision as of 11:55, 26 April 2023
Description
- Description:
- Returns the global namespace attached to config parser.
- Groups:
- NamespacesVariables
Syntax
- Syntax:
- parsingNamespace
- Return Value:
- Namespace
Examples
- Example 1:
Additional Information
- See also:
- missionNamespace uiNamespace currentNamespace profileNamespace localNamespace allVariables with Forward 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
- Posted on Jan 27, 2015 - 18:08 (UTC)
-
Any global variable defined in a config using __EXEC() will be stored in this namespace.
For example in the description.ext:
The variable "testVar" can be accessed during mission run time using getVariableThe above example would print 1.
This example however: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()