Two other methods not mentioned in the otherwise-excellent document Matt mentioned are use of a Global "Stop All" variable and a related use of a VIG/Functional Global Variable. The reason to mention them is that they can be used to additionally stop "detached" VIs, VIs that are set to run asynchronously (and thus somewhat "out of control") with respect to the main VI.
I'm using a "combination of ingredients" for some Projects I'm currently developing using LabVIEW 2016 and its support of Channels. For example, I use a Messenger Channel to create something analogous to a Queued Message Handler. When the Event Loop detects the Exit button has been pushed, it puts an "Exit" Message on the Messenger Channel and also stops itself. When the Message Loop sees "Exit", it sends an Exit Message on to whomever else needs to see it (in one case, the Producer of a Producer/Consumer pattern) and stops itself. When the Producer gets the Exit Message, it puts a "Last Element, Not Valid" on the Stream Channel to the Consumer, and stops itself. When the Consumer gets the Last Element message, it ends itself. A glorious cascade.
And I'm working out (not yet 100% complete) how to extend this to Start Asynchronous Calls, which don't (yet) support Channels as easily ...
Bob Schor
