stopping a VI when its FP is closed

[YoMetric]

I am having an issue getting the interaction i want between two VI's i have made.  I have a top level VI that lets the user choose some options for different tests to run.  When they make the choice a subVI opens (and in the block diagram of the top level VI it shows the called subVI with the green arrow signalling that it is running).  The test works fine with the subVI and when the user is done I would like them to be able to close the window.  However if you use the X in the corner to close this FP, the top level VI block diagram still shows this subVI as running and gets stuck there.

Everythign works fine if you hit the stop button in the subVI, the top level VI will continue as it should.  That would be good enough for me, but i know that other users will try to close the window and i cant let it freeze up the top level VI every time.

I guess what i am really looking for here is to be able to close the window of this subVI, but have it stop execution first so that the top level VI doesnt get stuck.

I have tried using an event structure that will trigger TRUE to be sent to the stop button when the front panel is closed.  The subVI seemed to just sit there waiting for the front panel to be closed rather than doing any of the rest of its procedure.  I think this may be due to the fact that i am using a state machine, it just doesnt seem to go on to the next state.  When I looked at it with highlight execution on it seems to be stuck at the event now.

Any enlightenment you can give on this issue would be greatly appreciated

[candidus · Accepted solution]

You can set the subVI's properties so that its frontpanel is not closeable:

This way you force the user to hit the stop button.

To get control over the subVI regardless in which state it is,

you can call it dynamically: Open a VI reference to it and use a "Call By Reference" node:

Now you're able to stop it via invoke node from another loop but that's

something you should avoid if you can.

Message Edited by candidus on 07-01-2009 07:32 AM

[TCPlomp]

Or you could register for the FP event in the sub VI (or even main VI), and finish the code inside the VI.

Ton

[YoMetric]

Making the VI non-closeable seemed like the simplest option.  That should work fine for my situation.  Thanks a lot for the quick responses

[elset191]

I absolutely hate having to press stop buttons.  So, I use the X button.  Make an event structure with the event Panel Close.  I wire a true out of this case into the stop terminal on the while loop.  Works wonderfully.

[elset191]

I should also note that if you don't want the front panel to close you can use the Panel Close? event and wire a true to the discard terminal.

[giancarlotamburello]

I have solved this problem in a different way (upper part). Remember to add a command that re-open the frontpanel when the vi is lunched (bottom part).

[altenbach]

---

@giancarlotamburello wrote:

I have solved this problem in a different way (upper part). Remember to add a command that re-open the frontpanel when the vi is lunched (bottom part).

---

You added to an 8 year old thread with a cryptic message. You probably want to explain to all of us in much more detail why you think this is a good solution. Your suggestion needs to constantly poll the front panel state with each iteration of the loop, which seems like a waste of resources.

[Станев]

So what is wrong?

I have just used @giancarlotamburello's code.

So far it seems to work for me.

[billko]

---

@Станев wrote:

So what is wrong?

I have just used @giancarlotamburello's code.

So far it seems to work for me.

---

Read the post right above yours.