09-07-2007 09:19 AM
09-07-2007 09:44 AM - edited 09-07-2007 09:44 AM
Message Edited by smercurio_fc on 09-07-2007 09:45 AM
09-07-2007 09:56 AM - edited 09-07-2007 09:56 AM
I am sure there is no way to create buttons on demand because I believe the button has to exist at the time the code is compiled before execution.
You could build an array of references to each of the controls. That way you can iterate through the array, send the reference to property nodes, and set the size, location, and visibility accordingly. However creating the 324 references the first time could be quite tedious.
I'm sure one of the more expert forum members has or knows how to use the more detailed class properties of the booleans to build the array of references more programmatically.
I see Smercurio has gotten an answer in quicker. I guess one question would makes a difference in coding is whether the boolean buttons would be a 2-D array (such as Smercurio posted.) Or whether you need to have the buttons be individual entities, in which case you need and array of references to each button (more in line of what I was thinking). If the user interface allows it, Smercurio's method using a button array would be much easier to work with programmatically. The question is how is the rest of your program using the values of the buttons.
Message Edited by Ravens Fan on 09-07-2007 11:02 AM
09-07-2007 10:02 AM
09-07-2007 10:09 AM
09-07-2007 10:10 AM
09-07-2007 10:27 AM
09-07-2007 10:31 AM
09-07-2007 11:34 AM - edited 09-07-2007 11:34 AM
Yes, Lynn is correct that you can not set the properties of individual items inside the 2-d array.
In reply #52 of this thread the example labeled "Obfuse Picture" creates 135 booleans with individual colors and labels.
Ben
Message Edited by Ben on 09-07-2007 11:34 AM