Making test code 'Fool Proof??' using an Abort type option

[jdebuhr]

I have created 2 different tests for the Techs where I work. I have both set-up with abort buttons so if something should happen it will abort the test. but every now and then it seems as if someone will close one of the prompts for the test by clicking the 'X' in the upper right. I know I can just do away with the title bar and MAKE them press the button on the front panel to continue but I am not sure I want to do that just yet. What I am curiouos on is if the prompt vi that is running is a subvi in my main program, is there a way to pass through some sort of output if the vi is closed by that 'X'? this way I could put the program into an idle state. allowing the user to select a new task in the program without having to close it and restart.

This program was made about a yer agao and since then I have learned more with LabVIEW and will be working on cleaning my code and improving it as there are some things I should address, but making it fool proof is at the top of my list.

I am hoping there is a way to allow the subvi to pass a boolean or something to know that the prompt window was closed prematurely and to go into an idle state. if not I will remove the title bar to fix that problem.

[Dennis_Knutson]

You can use the event structure to detect the "X" button (Event = Panel Close/) or the File>Exit (Event= Application Exit?) selection. There is a shipping example called Event Conditional Stop that shows both of these.

[jdebuhr]

Thanks I will look over the examples on monday and see how I can implement it.

[Dynamik]

Hi Dennis - the "discard?"  option is a nice feature - never noticed it - thanks for the pointer.