Also, you may have to wrap the event structure in a while loop to keep it running (waiting for an event), Wrap an event structure around your case structure. When the vi is run, nothing happens until the button is pressed (value change). The case structure then figures out what the new state of the button is (make sure the button is inside the event structure but outside the case structure)...and causes the case to run once. The button will stay down, until you choose to press it again, and when you do that, the event will fire again, the status of the button will select the appropriate case...and things will be back to normal.
Hope that is clear as mud...
I also went to the vi property window (right click on the vi icon in the upper right hand corner) and set the execution option for clear controls/indicators on start.
I then went to the text box and cleared it out, right clicked on it and went to Data Operations and Make this the dafault value.
Ben and the guys are trying to teach me how to use what they call a producer consumer architecture...basically, it would form a Queue with two loops. One loop would contain the event structure, the second loop would contain all the case structures. When you hit the button in that case, the event would fire, in that event you would put the case choice on into the Queue, and then the event would end, the queue would dump the case choice out at the front of the case structure and run it. Don't know if that would help you here though...
Hope this helps.
See the example.
H
