A question about tables
Hi there. I have a question about using tables in GS.
I understand how to create tables, imprt them, export them and write to them. I also know how to call on them for specific functions.
Is there a way to start with a table cell value? Am I missing something? I would like to have a rule that starts with a table cell value (if table - row 1/col 1 is true, then).
Is there any way to do this or a workaround trick that accomplishes the same goal? Otherwise I don't see much value in tables when I am better off just creating a bunch of attributes and setting them with the change attribute behavior.
Any help out there?
I understand how to create tables, imprt them, export them and write to them. I also know how to call on them for specific functions.
Is there a way to start with a table cell value? Am I missing something? I would like to have a rule that starts with a table cell value (if table - row 1/col 1 is true, then).
Is there any way to do this or a workaround trick that accomplishes the same goal? Otherwise I don't see much value in tables when I am better off just creating a bunch of attributes and setting them with the change attribute behavior.
Any help out there?
Comments
I will end up with hundreds of attributes. And somehow I dont think thats a an optimal way to do things. Or is it?
So my table looks like this: 66 rows, 4 columns. Column 1 & 2 are integers marking the x & y positions on my grid. Column 3 is a boolean for ticking an attribute on/off and column 4 is an integer between 1-6.
I understand how to write to these tables (in fact I do it a lot with my project). What I wan to do is to say, "If row 5, column 3 is set to true, then do stuff (change attributes, images, etc.)". But since I dont have access to the expression editor on the left side when creating a new rule, i cant seem to do this type of check.
Otherwise, as I said, I will have to create a bunch of attributes for this. A set for the positions, a set for the boolean in those positions and a set for the integer in those positions. It leaves me with hundreds of attributes.
I cant think of another way to check these positions without doing this.
I guess another question is this: Is it bad to have that many attributes? I mean that is a lot of data entry (not that I cant do it, its just a scary prospect), and if there is a better/more efficient way to accomplish this then I would rather do that.