Skip to content

How can I close LabVIEW programmatically if there are unsaved changes

Jump to bottom
viltbalint edited this page Oct 10, 2018 · 2 revisions
Background

Sometimes LabVIEW detects VI changes although it is not made by the developer. For example, in case of continuous integration (CI) "save changes" pop-up windows must be taken care of programmatically.

Possible solutions
  • Use command line call to close current LabVIEW process (see here).
  • Save all changes and close LabVIEW programatically (see here). Note that programatically save will not work on write-protected VIs.
  • Suppress modal windows via this VI. Disclaimer: this VI uses a private LabVIEW property and it is a persistent setting! Do not use this property (or disable it) in non-CI mode during production development!
Additional notes
  • An example project can be found on our public GitHub repository.
  • Auto recovery may be disabled to avoid modal window at the beginning of next LabVIEW start.
  • Auto recovery can be disabled via LabVIEW setting (Tools/Options/Environment/ section "Saving VIs", checkbox "Enable automatic saving for recovery"). This may work for a programmatic solution (untested).
  • The example VIs have been created using LabVIEW 2015.
Clone this wiki locally