Stop and Quit LabVIEW Vi

Question

I don't fully understand why I need the stop and quit labview vi.  When a program finish running, doesn't it stop automatically?  Why is the stop vi needed?  If vi stops automatically when it is done, couldn't the programmer write the program in such a way that would cause the vi to stop when needed without using the stop vi? 
When a program is running in exe, why is quiting labviw needed?  Doesn't everything quit at the end of the program?  In development, there is really no reason for the developer to want the LabVIEW to quit automatically, right?
Kudos and Accepted as Solution are welcome!
Solved!
Go to Solution.

Answer 1

jyang72211 wrote:
When a program finish running, doesn't it stop automatically?  Why is the stop vi needed?
You never need the stop.vi. Its function is similar to the abort button, unconditionally stopping the VI, even if it is trapped in a parallel loop that cannot be stopped directly due to incorrect coding. Since the current state of other code parts is random when stop is called, the outcome might be very unpredictable and the program might stop without a proper shutdown sequence, leaving your instrument spinning or the hight voltages turned on.
For more details, read the online help. I never use it!
"Quit LabVIEW" has similar problems. You don't really want to use it during development, because, you might have unsaved changes.
My larger applications don't have a stop button, and can only be stopped with the [X] in the upper right corner. (Like any typical program: When was the last time you had to first "stop" internet explorer or MS word? :d) I use a filtering event to catch it, discard it, initiate a clean shutdown, and after everything is done, either stop in the development system or quit labview in the case of a built application (see code image).
LabVIEW Champion . Do more with less code and in less time .
Attachments:
FinishApp.png ‏4 KB