From Friday, January 17th 11 PM CDT (January 18th 5 AM UTC) through Saturday, January 18th 11:30 AM CDT (January 18th 5:30 PM UTC), ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
@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.
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?
@Mark_Yedinak wrote:
@Kevin_Price wrote:
If you can't persuade them from not doing the thing that's bad for 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.
You could obtain a reference to their vi and take the abort button off of their tool bar. A bit malicious but it forces them to not use the abort button. I'm not sure that it would fix your problem, though, as they would likely just program in a new abort button.
On a more serious note, could you make your application run asynchronously and check when the caller vi stops running? The vi that you make open for them to call would just be a wrapper to call and forget your asynchronous vi. You could give your asynchronous vi a reference to the calling wrapper, and let the wrapper run until they abort. It would be easy enough to provide functionality for proper shutdown later. It's not ideal (would be better if they would follow reasonable programming practices), but it might be a workaround.
@Eric1977 wrote:
@RTSLVU wrote:
Except try to implore them that they should not be running in the development environment anyway.
This is the real question that needs answered. Why are they running this in the Development Environment and not a exeuteable? Or does the EXE have the Abort button being shown?
Anecdotally, in its early years, LabVIEW didn't have the option of creating an executable.
