Running VI with a Boolean Button in the Front Panel

[Manuel_Ruiz]

Hello,

First of the all sorry for my bad writting, I know I need improve my english.

I don't know how difficult it would be implement this idea, but it would be useful

to have the option of running your VI with a boolean Button within your Front Panel

instead of .

Without making any changes in your Block Diagram, only with right click menu in your

Front Panel.

Regards and Happy New Year.

[altenbach]

This has been discussed many times in the LabVIEW forum. A Vi in edit mode has no place in a final deployment. Set the VI to run when openend and have it start out in an idle state of a proper state machine. Now you can use any LabVIEW control to go to a different state.

Of course it can be done using current tools, but it makes no sense. Read the entire thread.

[Manuel_Ruiz]

Hi, altenbach.

I have seen many users asking for this option in the LabVIEW forum, therefore I think it would be a nice idea implement this in futures LabVIEW versions for two big  reasons:

1. Save time.
2. Simplify the work.

I know it can use a state machine for this, but some new LabVIEW users don't know how to implement it, and they spend a lot of time on this task.

[altenbach]

No, edit mode is edit mode. We need to be able to operate anything on the front panel in edit mode without the danger of the VI starting unexpectedly.

The run button is only a tool used during code development. It has no purpose in a final deployed application. When was the last time you had to start or stop MS word or internet explorer? A normal application is either running or closed. Period. Just because ignorant LabVIEW beginners ask for this, does not mean it is a good idea.

It does not "save time". we already have a run button, so adding another one and configuring it takes extra time and programming effort. Now we have duplicate functionality and are confusing the user because he is not sure if there is a difference between using the real run button or that fake run button. The next program he uses only has the regular run button and he suddenly does not know what to do.

It does not "simplify the work". It adds additional complexity. Learning how to build a state machine takes minutes, there is even a template that ships with LabVIEW. Learning to do it the right way from the beginning saves huge amounts of development time in the future.

[AristosQueue (NI)]

R&D is considering many feature requests that would make the line between edit time and run time more distinct. This feature request would be moving in the wrong direction.

[Darren]

Any idea that has not received any kudos within a year after posting will be automatically declined.