Visibility & run

[gireesh]

In my new project I am planning to design as some of the menus will visible at the time of required testing. For this a dropdown menu arranged. At runtime we can select the appropriate test. My doubt is during runtime default values will take as input. We should change the inputs during runtime. Changed input values only should go for process. Without disabling the default values how will write the program?

[RavensFan]

Do you have a doubt meaning you don't believe you can do something?  Or do you have a question, where you want to ask how to do something?

If your issue is that when you start your VI, you have default values defined in controls and you don't want your code to run until you've had a chance to change your controls, then you just need to program it that way.  Have your VI start, but be in a loop where you do any preliminary things (like update a menu based on the value in a control), and that loop will stop whenever your user has hit some sort of Go button, at which time the while loop ends, and your program will enter into the next portion of your code where all the real work of the program is done.

[gireesh]

Sorry for the mistake about doubt & question. Thank you for the help

[gireesh]

Now the real problem comes. Start/go button will come only once. The program is in RUN state. How to program this?

[tbob · Accepted solution]

Like this:

[gireesh]

Very very thank you for this help

[gireesh]

One more - after the loop the main programs will work, OK fine. My question is after running the program can we connect to the first loop, so the program never stop without hitting the main stop button. I tried but it is showing - wire from the same loop.

[tbob]

Put a while loop around the entire VI and add a stop button to stop the big loop.  When your code finishes running, the VI will wait for the GO button to start again, or for the Stop button to stop the program.

[gireesh]

Oh no this much simple. I thought it in another way that is the reason for this question. Thank you for the help

[RavensFan]

If your looking for a Go, Stop, Go, Stop, Exit for good type of architecture, now you really need to get away from the separate loops.  Because if you hit the big stop button while you are in your initial waiting to run loop, your program won't end until you hit the Go, then the Stop button.

At this point you should be looking into a state machine architecture where you have at least 2 states of  Wait and Run, and hitting your Exit button would allow you to get out of either state as the case may be.