LabVIEW
LabVIEW Abort Button
@Mark_Yedinak wrote:
@billko wrote:
@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.
And I had to install it from floppy disks. I remember prompts like "Please insert disk 15 or 20". Those were the days. Can't forget no undo either.
Sounds like you have been doing LabVIEW for about as long as I have. Don't forget that there was also no event structure.
@Mark_Yedinak wrote:
@meBaga wrote:
Thank you all for the suggessions, To answer the question asked in the comments, I'm going to deliver the API and the user is going to use it in labVIEW development environment to create his own program.
I have found a work around. I'm launching a background thread dynamically which will be monitoring the launching VI state as running or not. based on that I can close the hardware referance. As of now concept is working. I'm going to give it a try tomorrow with the real software.
While this might be a viable work around, you really should educate your client on the dangers of using the abort button to stop the VI. It is a terrible and potentially dangerous, life threatening method for stopping an application. Yes, it could be that serious.
It should only be used as a last resort when debugging and the VI has become completely unresponsive. In all other cases a graceful shutdown should be used.
It appears that meBaga has already communicated this to the customer, but they've been doing it like this for years and aren't going to stop now. I'm guessing that they're not working with anything life-threatening in this case. I think that the approach that meBaga is taking is unfortunately the best given the circumstances (aside from perhaps walking away from the job). At least his/her part of the program will have a graceful shutdown.
I would still put something in the agreement that says you aren't responsible for what happens if the abort button is used as a normal way of stopping the code. I mean, this is like shutting down your computer by pulling the plug out of the wall.
@paul_cardinale wrote:
@johntrich1971 wrote:
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.
I actually don't have a problem with that kind of 'malice'.
I really don't either, but I think that they would just put a STOP button on the screen that does essentially the same thing - so it really doesn't do anything unless they let the OP help them program a proper shutdown.
