LabVIEW
SURE FIRE WAY of KILLING (STOPPING) a LabVIEW-based EXE APPLICATION
Solved!
Maybe the VI isn't running but you haven't closed LabVIEW. When the program should stop, do you see the LabVIEW toolbar (with the white run arrow)?
In that case you need to call the "Quit LabVIEW" VI.
I use this simple VI at the end of each of my applications to be sure that the window (and therefore process) close properly
@Basjong53 wrote:
Maybe the VI isn't running but you haven't closed LabVIEW. When the program should stop, do you see the LabVIEW toolbar (with the white run arrow)?
In that case you need to call the "Quit LabVIEW" VI.
I use this simple VI at the end of each of my applications to be sure that the window (and therefore process) close properly
I feel that (nowadays) this is a crutch. If you have to use this, you're doing something wrong. Pre-LV 7.0, you had to use it to properly exit an app.
@billko wrote:
@Basjong53 wrote:
Maybe the VI isn't running but you haven't closed LabVIEW. When the program should stop, do you see the LabVIEW toolbar (with the white run arrow)?
In that case you need to call the "Quit LabVIEW" VI.
I feel that (nowadays) this is a crutch. If you have to use this, you're doing something wrong. Pre-LV 7.0, you had to use it to properly exit an app.
Really? It has never given me any problems. What is the modern way to do it? Use the FP.Close invoke node on the main window?
A built executable will stop execution as soon as all its windows (front panels) are closed. But remember that a hidden front panel is NOT closed.
However if you close the last front panel, the LabVIEW process terminates immediately, without waiting to pass through Go. 😁 At least that was the case until a few versions ago. Maybe someone added some extra respite period to it if there was still a VI running somewhere.
Your loop trying to do some important and absolutely needed cleanup at the end may simply get yanked out of existence midway. So make sure to only close your last front panel after you are really done with any important things.
@rolfk wrote:
A built executable will stop execution as soon as all its windows (front panels) are closed. But remember that a hidden front panel is NOT closed.
However if you close the last front panel, the LabVIEW process terminates immediately, without waiting to pass through Go. 😁 At least that was the case until a few versions ago. Maybe someone added some extra respite period to it if there was still a VI running somewhere.
Your loop trying to do some important and absolutely needed cleanup at the end may simply get yanked out of existence midway. So make sure to only close your last front panel after you are really done with any important things.
I always merge the error wires coming out of all the parallel loops and use the output of the merge to enforce dataflow. I put things like destroying references and events - and closing the top level front panel - after the merge to make sure everything is "done" before I go and destroy stuff, with the very last thing being closing the FP if it's an executable.
@Basjong53 wrote:
Maybe the VI isn't running but you haven't closed LabVIEW. When the program should stop, do you see the LabVIEW toolbar (with the white run arrow)?
In that case you need to call the "Quit LabVIEW" VI.
I use this simple VI at the end of each of my applications to be sure that the window (and therefore process) close properly
It works just like the STOP vi (or the abort button) so it comes with the same caveats.
