Problem with widget creation and alterable values

[Jacob]

Yeah. I usually get around that by having an ID value that is spread through all instances of an object, and then use an array to store values. You can test for the X Index of the array to = The ID of the instance, and then the Y values would be different alterable values that you can use. It pretty much unlimits you, but it's a hassle that really shouldn't be there.

[Outcast]

Yeah. I usually get around that by having an ID value that is spread through all instances of an object, and then use an array to store values. You can test for the X Index of the array to = The ID of the instance, and then the Y values would be different alterable values that you can use. It pretty much unlimits you, but it's a hassle that really shouldn't be there.

Hmm.. i am not sure I follow, do you have an example of this? Is this method for storing unlimited alterable values? Is it much slower then the regular method? Do you load values from the array into the alterable value slots or do you just refer from the array in all calculations with the values?

[Jacob]

You just refer from the array. You would have expressions like ValueXY("Array", [ID], [Value Index]) or something similar (I forget what the actual syntax of the array object is).

So if your object has an ID of 3 and you want to access the seventh stored value, you would use ValueXY("Array",3,7)

It's a little messy and ugly but it does the job. That said, this shouldn't be necessary in the first place and alterable values shouldn't be limited anyway.