with: Difference between revisions
(adapted page by stating with as an operator on it's own) |
Sarogahtyp (talk | contribs) mNo edit summary |
||
Line 9: | Line 9: | ||
| Creates a [[With Type]] that is used inside a [[do]] construct in order to execute code inside a given namespace. | | Creates a [[With Type]] that is used inside a [[do]] construct in order to execute code inside a given namespace. | ||
{{warning | when used in a do-construct in scripts with allowed suspension, an unexpected namespace switch could happen (see note below)}} | {{warning | when used in a do-construct in scripts with allowed suspension, an unexpected namespace switch could happen (see note below)}} | ||
'''NOTE''' for the reasons unknown, namespace switching might unexpectedly occur inside some scopes ([[for]], [[if]], [[try]], [[call]]) started in scheduled scripts ([[canSuspend]] true) after small suspension if [[with]] was not the main scope. For example: | '''NOTE''' for the reasons unknown, namespace switching might unexpectedly occur inside some scopes ([[for]], [[if]], [[try]], [[call]]) started in [[Scheduler#Scheduled_Environment|scheduled]] scripts ([[canSuspend]] true) after small suspension if [[with]] was not the main scope. For example: | ||
<code>[] [[spawn]] | <code>[] [[spawn]] | ||
{ | { | ||
Line 51: | Line 51: | ||
}; | }; | ||
};</code> | };</code> | ||
To eliminate possibility of error you can also use [[setVariable]] or [[getVariable]] with desired [[Namespace]], which is also scheduled environment save. | To eliminate possibility of error you can also use [[setVariable]] or [[getVariable]] with desired [[Namespace]], which is also [[Scheduler#Scheduled_Environment|scheduled environment]] save. | ||
|= Description | |= Description | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ |
Revision as of 13:18, 20 June 2017
Description
- Description:
- Creates a With Type that is used inside a do construct in order to execute code inside a given namespace.
NOTE for the reasons unknown, namespace switching might unexpectedly occur inside some scopes (for, if, try, call) started in scheduled scripts (canSuspend true) after small suspension if with was not the main scope. For example:
To eliminate possibility of error you can also use setVariable or getVariable with desired Namespace, which is also scheduled environment save.[] spawn { with uiNamespace do { for "_i" from 1 to 1 do { systemChat str [ currentNamespace isEqualTo uiNamespace, currentNamespace isEqualTo missionNamespace ]; // result [true, false] sleep 0.05; //<-- small suspension systemChat str [ currentNamespace isEqualTo uiNamespace, currentNamespace isEqualTo missionNamespace ]; // result [false, true] <-- switching }; }; };
However if with used in parent scope, everything works correctly:with uiNamespace do { [] spawn { for "_i" from 1 to 1 do { systemChat str [ currentNamespace isEqualTo uiNamespace, currentNamespace isEqualTo missionNamespace ]; // result [true, false] sleep 0.05; //<-- small suspension systemChat str [ currentNamespace isEqualTo uiNamespace, currentNamespace isEqualTo missionNamespace ]; // result [true, false] <-- NO switching }; }; };
- Groups:
- Uncategorised
Syntax
Examples
- Example 1:
_myWithType = with uiNamespace;
- Example 2:
with missionNamespace do {global = global + 1};
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