Add a new variable. This can be costly, don't use in performance sensitive paths.
Variable name
The variable to be added
Get a variable.
The variable's name
The specified variable. If not found, an empty variable is added to the container.
Get a variable using its index. If you're unsure about how to use this method, prefer to use get
.
The index of a variable is its index in the data passed to initFrom.
This method is generally used by events generated code to increase lookup speed for variables.
The variable index
The specified variable. If not found, an empty variable is added to the container, but it should not happen.
Check if a variable exists in the container.
The variable's name
true if the variable exists.
Check if a variable exists in the container.
The variable
true if the variable exists.
Initialize variables from a container data.
If keepOldVariables
is set to false (by default), all already existing variables will be
erased, but the new variables will be accessible thanks to getFromIndex.
if keepOldVariables
is set to true, already existing variables won't be erased and will be
still accessible thanks to getFromIndex.
The array containing data used to initialize variables.
Remove a variable. (the variable is not really removed from the container to avoid creating garbage, but marked as undefined)
Variable to be removed
"Bad" variable, used by events when no other valid variable can be found. This variable has no state and always return 0 or the empty string.
"Bad" variable container, used by events when no other valid container can be found. This container has no state and always returns the bad variable ( see VariablesContainer.badVariable ).
Generated using TypeDoc
VariablesContainer stores variables, usually for a a RuntimeGame, a RuntimeScene or a RuntimeObject.