There's a lot going on here that perhaps you haven't considered. When your app is an exe, how will you store the settings so that they can be recalled later? You probably need to save them to a config file and then read them upon startup. Also, you need to decide on a storage mechanism of your variables that is internal to your program. You can use a local variable as stated to read the array but then how do you pass it throughout your app? Wires and shift registers come to mind but you might want to consider functional globals. Here is a link to a post I made way back that has a working example code of what you might want to do:http://forums.lavag.org/index.php?s=&s...post&p=8956
Notice that, once the configuration panel is closed, the configuration is available from anywhere in the program via the functional global. If you look inside the functional global you will see a state that handles saving of the configuration. Here is where you would implement your preffered method of configuration saving so oan executable can read it. This design pattern may seem trivial but it works.