If you have ever built a VI that uses the native Quit LabVIEW function, then you have most likely had to deal with LabVIEW closing while you are developing or debugging your VI or any of its sub VIs. Nothing is more frustrating than making changes to several sub VIs, checking that the changes work as expected when the changed code is executed as part of your main VI and then watching LabVIEW close -- just as you remember that you did not save those changed VIs.
So, how do you keep LabVIEW from closing when you need to edit or debug your main VI or any of its sub VIs? Some typical methods for preventing LabVIEW from closing when developing or debugging your code are to remove the Quit LabVIEW function temporarily, write code to disable it or set a breakpoint before you call the Quit LabVIEW function. Then you must remember to undo those changes when your development work is complete. The Quit LabVIEW (Conditional) VI can help to reduce this frustration.
The Quit LabVIEW (Conditional) VI quits LabVIEW if the number of VIs in the caller's hierarchy and the number of VIs currently in memory is equal (This means that no other VIs are in memory, so it's safe to quit LabVIEW). Otherwise the Quit LabVIEW (Conditional) VI takes the action on the caller's front panel as specified by the "Action if not quitting LabVIEW" input. Run the included example VI to see how you can use this functionality in your applications.