LabVIEW Abort Button

[meBaga]

I'm Craeting a Hardware Interface API and providing my customer easy tools to use LabVIEW. Note that my customer is not an expert in LabVIEW and they tend to use Express VIs and Abort Buttons frequently. 

I'm making my own express VI using the Hardware API and it works fine for me. I need to know if there is any way that I can detect  that the top level Aplication program (made by the customer) is aborted by pressing the abort button, so that I can close my device referance gracefully, and it opens properly next time. (presently If I press abort, I need to unplug the device before using next time).

I checked this -

How to detect Front Panel ToolBar Abort Button? - NI Community

But not much help.

I tried to explain techanicality to my customer, but the counter argument I got is that the same behaviour works with NI DAQ. If we abort, it will still work properly next time.

Any help will be appreciated. 

[billko]

---

@meBaga wrote:

I'm Craeting a Hardware Interface API and providing my customer easy tools to use LabVIEW. Note that my customer is not an expert in LabVIEW and they tend to use Express VIs and Abort Buttons frequently. 

I'm making my own express VI using the Hardware API and it works fine for me. I need to know if there is any way that I can detect  that the top level Aplication program (made by the customer) is aborted by pressing the abort button, so that I can close my device referance gracefully, and it opens properly next time. (presently If I press abort, I need to unplug the device before using next time).

I checked this -

How to detect Front Panel ToolBar Abort Button? - NI Community

But not much help.

I tried to explain techanicality to my customer, but the counter argument I got is that the same behaviour works with NI DAQ. If we abort, it will still work properly next time.

Any help will be appreciated. 

---

Counter that by saying that using the abort button is a highly discouraged LabVIEW practice and you will not cannot provide support for your software if this is a requirement.

[Kevin_Price]

If you can't persuade them from not doing the thing that's bad for them...

Prevent them!

(As mentioned in the linked thread, you can remove the Abort button from the toolbar and provide them a safer way to stop).

-Kevin P

[Mark_Yedinak]

---

@Kevin_Price wrote:

If you can't persuade them from not doing the thing that's bad for them...

Prevent them!

(As mentioned in the linked thread, you can remove the Abort button from the toolbar and provide them a safer way to stop).

-Kevin P

---

This would not solve his problem because I believe he is supplying a library and the client is in control of the top level VI.

You could always tell your customer that using the abort button is the same thing as stopping your car by running into a brick wall. It works, but the outcome is certainly not desirable.

[FireFist-Redhawk]

AFAIK there is no way to do what you're asking. Which is why everyone is trying to convince you, to convince your customer, to not click the abort button.

What would even detect the abort button click if everything stops when you press it?

[RTSLVU]

---

@meBaga wrote:

I tried to explain techanicality to my customer, but the counter argument I got is that the same behaviour works with NI DAQ. If we abort, it will still work properly next time.

Any help will be appreciated. 

---

Try explaining it this way...

You are a passenger in a car traveling 60 MPH and you tell the driver to stop.

Pressing the Stop button:

1. The driver presses the break.
2. Allows the car to come to a complete stop
3. Puts it in park
4. Turns off the engine
5. Gets out of the car.

Pressing the Abort button:

1. The driver just opens the door and bails out at 60 MPH 

What car would you rather be riding in?

Honestly I don't think there is much you can do. Except try to implore them that they should not be running in the development environment anyway. If they were running a compiled executable you could hide the abort button and catch the "panel close" event and do a proper shutdown if they just closed the program.