LabVIEW
To exit the Labview program
To add one small part to the story, I would like to add that everything dies eventually!
So here it comes.... Everyone SHOULD be putting in at least one EXIT vi in a production application!
Still sat in your seat?
I can almost see your point if you deploy your production applications as VIs (not executables) on machines that have the LabVIEW development environment installed (I hope you have a license for each those machines, watch out when the next version is released), but if you build them to executables, the runtime engine shuts down as soon as the top level VI in the application is closed. So there's really no need for it.
If you are deploying applications as VIs, then it might make sense to use the Exit function, but only after first making sure all your hardware is in a safe state. It depends on what the user is expecting. I've built many applications that run in the development environment that run in engineering labs and the users expect LabVIEW to stay open so they can get to other applications without having to restart LabVIEW.
Our production applications we build for external customers are built following a standard coding procedure that we have adopted from many different sources. And we try to do a code review on them as well to try and catch anything we might have missed. Though far from perfect, it gradually gets better the more we do it.
Now my questions to the forum are: -
Do you allow for and provide, a single point of software shutdown; clearly stated and explicitly defined for production applications (would you admit you don't / haven't)?
If you don't; what do you do?
How do you go about trying to assure clean up of any problems (I have yet to meet the perfect systems designer, I live in hope).
Ed
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
