allVariables – Talk

Latest revision as of 11:53, 11 January 2023

Let's assume that you're using global variables (since I'm not sure if local variables are actually in any namespace). setVariable is simply a handy means of setting a variable, so it would return the variables in your first and second example as well as if you had used missionNamespace setVariable ["myVariable",0]. --SilentSpike (talk) 21:20, 12 December 2014 (CET)

Creating a global variable automatically sets it into the missionNamespace:

someVar = "Hello, world";
hintSilent format ["%1", missionNamespace getVariable "someVar"]; //result: "Hello, world"

So there's no need for that. You can overwrite variables in the namespaces, just as you can overwrite global variables by reassigning them. But if you create objects which are global by default (like triggers), you can overwrite their reference (as variables are called by reference), but this will not overwrite the object itself:

myFancyTrigger = createTrigger ["EmptyDetector", getPosATL player];
_trigger = createTrigger ["EmptyDetector", getPosATL player];
missionNamespace setVariable ["myFancyTrigger", _trigger];

In fact, after this, there will still be both triggers, though the missionNamespace only knows the last one. The same thing would happen if you assigned the created trigger to a global variable and overwrite that. --Johnny

@@ Line 1: / Line 1: @@
-I don't really play around on the dev build so I'm a little confused with this command. Does it return all variables or only the ones created with [[setVariable]]?
+:Let's assume that you're using global variables (since I'm not sure if local variables are actually in any namespace). [[setVariable]] is simply a handy means of setting a variable, so it would return the variables in your first and second example as well as if you had used <code style="display: block">missionNamespace setVariable ["myVariable",0]</code>. --[[User:SilentSpike|SilentSpike]] ([[User talk:SilentSpike|talk]]) 21:20, 12 December 2014 (CET)
-for example:
+::Creating a global variable automatically sets it into the missionNamespace:
-<code>_myVariable = 0;
+::<code style="display: block"><nowiki>someVar = "Hello, world";
-'''//same as'''
+hintSilent format ["%1", missionNamespace getVariable "someVar"]; //result: "Hello, world"</nowiki></code>
-with missionNamespace do
+::So there's no need for that. You can overwrite variables in the namespaces, just as you can overwrite global variables by reassigning them. But if you create objects which are global by default (like triggers), you can overwrite their reference (as variables are called by reference), but this will not overwrite the object itself:
-{
+::<code style="display: block"><nowiki>myFancyTrigger = createTrigger ["EmptyDetector", getPosATL player];
-	_myVariable = 0;
+_trigger = createTrigger ["EmptyDetector", getPosATL player];
-};</code>
+missionNamespace setVariable ["myFancyTrigger", _trigger];
-I guess I don't understand how the different namespaces work either. Would this command return ["_myVariable"] in both cases? - [[User:DreadedEntity|DreadedEntity]] ([[User talk:DreadedEntity|talk]]) 20:50, 12 December 2014 (CET)
+</nowiki></code>
-:Let's assume that you're using global variables (since I'm not sure if local variables are actually in any namespace). It would return all variables in the namespace, [[setVariable]] is simply a handy means of setting a variable. So for example, it would return the variable in your first and second example. It would also return the variable in your second example if you had simply declared it in the default namespace (which happens to be [[missionNamespace]]).
+::In fact, after this, there will still be both triggers, though the missionNamespace only knows the last one. The same thing would happen if you assigned the created trigger to a global variable and overwrite that. --[[User:Heeeere's Johnny!|Johnny]]

allVariables – Talk

Latest revision as of 11:53, 11 January 2023

Navigation menu

Search