03-18-2008 09:43 AM
03-18-2008 09:54 AM
Hello,
You may want to avoid using recursion. It can be done by calling the VI dynamically, but this particular problem can be solved without recursion. I would create a high-level VI that is not a dialog in itself - instead it is a state-machine that manages navigating between the different dialogs. In addition, this top-level VI can store the current selections made by the user in shift registers. Each dialog would be executed in one of the states of this top-level VI.
If you want images, and radio buttons, you'll probably want to create your own dialog VI. Based on inputs that you send it, you could have it display the appropriate pictures, provide the appropriate options, etc.
I'm not sure where you'd find a good example. I personally would typically implement this kind of heavily user-interface-driven application in C# or C++, but if LabVIEW if your bag then good luck.
Rob
03-18-2008 11:13 AM
Just a couple of notes on what Rob said:
You can set your main VI to be transparent, that way the user never sees anything but the dialog VIs.
You can set the various dialog VIs to be modal, and alter their practical appearance (scrollbars, size, file menus, etc) in the File->VI Properties menu. You can also set background images and create custom controls if you want to change the physical appearance.
I do agree the state machine is the best way to do it.