parsingNamespace: Difference between revisions
Jump to navigation
Jump to search
(add. ArmA2 classification) |
m (Command Group: Variables) |
||
| (11 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{Command|= Comments | |||
____________________________________________________________________________________________ | |||
| arma2 |= Game name | |||
|1.00|= Game version | |||
____________________________________________________________________________________________ | |||
| Returns the global namespace attached to config parser. |= Description | |||
____________________________________________________________________________________________ | |||
| '''parsingNamespace''' |= Syntax | |||
|p1= |= PARAMETER1 | |||
|p2= |= PARAMETER2 | |||
|p3= |= PARAMETER3 | |||
| [[Namespace]] |= RETURNVALUE | |||
|x1= <code>'''parsingNamespace''' [[setVariable]] ["var1",101.23124]; | |||
_profVar1 = '''parsingNamespace''' [[getVariable]] "var1";</code>|= EXAMPLE1 | |||
____________________________________________________________________________________________ | |||
| [[missionNamespace]], [[uiNamespace]], [[currentNamespace]], [[profileNamespace]], [[with]], [[ArmA:_Editing#Forward_Compatibility|Forward Compatibility]] |= SEEALSO | |||
| |= MPBEHAVIOUR | |||
____________________________________________________________________________________________ | |||
}} | |||
<h3 style='display:none'>Notes</h3> | |||
<dl class='command_description'> | |||
<!-- Note Section BEGIN --> | |||
<!-- Note Section END --> | |||
</dl> | |||
<h3 style='display:none'>Bottom Section</h3> | |||
[[Category:ArmA 2: New Scripting Commands List|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | ||
[[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Scripting_Commands_Take_On_Helicopters|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]] | |||
[[Category:Command_Group:_Variables|{{uc:{{PAGENAME}}}}]] | |||
<!-- CONTINUE Notes --> | |||
<dl class="command_description"> | |||
<dd class="notedate">Posted on January 27, 2015 - 18:08 (UTC)</dd> | |||
<dt class="note">[[User:BrotherhoodOfHam|BrotherhoodOfHam]]</dt> | |||
<dd class="note"><br/>Any global variable defined in a config using __EXEC() will be stored in this namespace.<br/> | |||
For example in the description.ext:<br/> | |||
<code>__EXEC(testVar = 1);</code> | |||
The variable "testVar" can be accessed during mission run time using [[getVariable]] | |||
<code>[[hint]] [[str]] ([[parsingNamespace]] [[getVariable]] ["testVar", 0]);</code> | |||
The above example would print 1.<br/><br/> | |||
This example however: | |||
<code>__EXEC(_testVar = 1);</code> | |||
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() | |||
</dd> | |||
</dl> | |||
<!-- DISCONTINUE Notes --> | |||
Revision as of 22:34, 23 August 2015
Description
- Description:
- Returns the global namespace attached to config parser.
- Groups:
- Uncategorised
Syntax
- Syntax:
- parsingNamespace
- Return Value:
- Namespace
Examples
- Example 1:
parsingNamespace setVariable ["var1",101.23124]; _profVar1 = parsingNamespace getVariable "var1";
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 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()