front panel of SubVI locks on 2nd call

[AndyBE]

HI!

I'm calling a SubVI and pass a Boolean Reference to this SubVI. In the SubVI I'm executing a While loop. The stop condition is the value of the boolean control in the VI that calls the SubVI. (Boolean Refnum + Property Node: VALUE connected to while stop condition)
Mechanical Action of the Boolean in the calling VI is: Switch when pressed.

For the first time this will be executed it works fine. But the 2nd time the SubVI is called. The Front Panel of the calling VI where the stop button is located will be locked.

Does anybody have an idea why this happens and how I can solve that problem?
ANDY

[tbob]

I tried what you described, using LV 7.1, and I have no problems running the vi over and over again. See the attached examples. Ref1.vi calls Ref2.vi and passes the Boolean reference to it.

[AndyBE]

HI,
I'm working with 6.1. But this makes not really a difference. I did already a small example VI quite similar to the VI that you have posted. There I havn't had that problem, too. But in the big main programme I do get those problems. In that programme there is a Case structure. In one case I have an Event structure. In the other case I have the SubVI that I'm calling. Somehow it seems that the Event structure even it should not be involved at all interferes with the rest of the program and locks the event structure (there is one event which is triggered from the same button as from which I want to stop the subVI).
That is only a guess from my side. Could that be a problem?
ANDY

[tbob]

It could be that the event is locking up and never allowing the bool value to be sent to the sub-vi. Post a sample of your code so we can look at it. Or maybe you could separate the event by using a different boolean and then running the code again to see if this is the problem.

[AndyBE]

HI!
Thanks for your input. That is exactly what I think. The event structure controls the boolean even if it is not executed. I havn't examined it further and placed a second boolean on top of the other boolean as you suggested it, too. Then I am controlling the visibility of both boolean according to the case that is executed.
ANDY