I have seen a bunch of triggers about data tables, but I don't think I have had any use for them... which brings me to my question of why do people use data tables versus global variables or whatnot?
When you create a Data Table you can store various variable types in it using a reference string, representing the column in a table. So instead of having e.g. 5 unique variables, or worse arrays, you need just one variable, the Data Table.
If you want to store the name of several units, for instance, you can use the reference string combined with an integer; the integer being the row ID. This is very handy in loop scenarios, e.g. during map initialization: "(UnitName + String(IntegerA))"
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I have seen a bunch of triggers about data tables, but I don't think I have had any use for them... which brings me to my question of why do people use data tables versus global variables or whatnot?
@sangeli: Go
When you create a Data Table you can store various variable types in it using a reference string, representing the column in a table. So instead of having e.g. 5 unique variables, or worse arrays, you need just one variable, the Data Table.
If you want to store the name of several units, for instance, you can use the reference string combined with an integer; the integer being the row ID. This is very handy in loop scenarios, e.g. during map initialization: "(UnitName + String(IntegerA))"