I'm not sure about changing the position, but you can make the visible/invisible by using a property node.
Right click> Create>Property Node
Then Right click on the node and click "Change to Write"
Thenk you can write True or False to it to make it appear/dissapear.
Are you looking to change the position of the button/control depending on the function within the vi? You may have to use seperate controls (making the ones you don't want invisible) to make this occur. Someone else may be able to help better!
If you know the maximum number of buttons you'll need, the easiest thing to do is to create them all on the front panel, then manipulate the Visible and Position properties as Evan and seanpatrick have said.
If you want to create a control programatically, that gets a lot messier. Look at the discussions here.
Man, you are having too much fun! I think Labview is fun, but none of my programs make me laugh. Thanks!
One interesting thing on a more technical note: The speed of your flying boolean is affected by the size of the window. If you maximize the window, the flying noticably slows down. If you reduce the size of the window, it really speeds up. I guess it's something inefficient in the way Labview or Windows redraws the window: a lot more is getting redrawn than just the area that changed.
I am glad you liked them. The folks around the office had a real hoot too.
I am not sure how LabVIEW refreshed the screen in the event cannon. I am sure there are several places I could improve the performance of my algorithm. I have been meaning to add code to programatically determine where the LED will be for its entire flight when the mouse button is clicked. This way I could add more target buttons and tell which button will be hit. This should speed up the code and add much flexibility. I wanted to call the additional code the LabVIEW game engine. So many plans, so little time...
Two of these use event structures not available in LV 6.0.2, but one of them is possible to transliterate. This is actually a rebuild of the code, apologies to Mr. Braden, I've attempted to make no changes to it's structure.
Why didn't I just save a prior version from 6.1? It's a long story...