LabVIEW
Close and open subVIs from main VI
First of all, you really need to Unregister your events. It works just fine then.
Secondly, you don't need to register for the panel close. It is in the event list already.
Give this mod a try.
@camerond wrote:
@billko wrote:
@camerond wrote:
Here's an easy way to do it, using a WHILE loop, T/F Case structures and local variables.
Cameron
It may be an easy way to do it, but it's basically bad programming. You shouldn't use while loops to poll buttons when you can make it event-driven.
But if he's confused with events, this does work. It may not be the most elegant solution, but that doesn't make it "bad" programming unless it interferes with his tasks. Computers are so fast and have so much memory now, that you don't always have to do things the most efficient way to get them done. Just IMHO, it's better to help someone with something he can understand than to give him a black box with magic inside, unless his goal is to learn the magic now.
TIMTOWTDI.
Cameron
Understood, but teaching someone bad habits is not good, either. Best to learn the right way or it will cause problems down the line.
[edit]
Granted that a QMH might be too complicated for a beginner, but then a simple event-driven structure would've been a better choice.
@billko wrote:
@camerond wrote:
@billko wrote:
@camerond wrote:
Here's an easy way to do it, using a WHILE loop, T/F Case structures and local variables.
Cameron
It may be an easy way to do it, but it's basically bad programming. You shouldn't use while loops to poll buttons when you can make it event-driven.
But if he's confused with events, this does work. It may not be the most elegant solution, but that doesn't make it "bad" programming unless it interferes with his tasks. Computers are so fast and have so much memory now, that you don't always have to do things the most efficient way to get them done. Just IMHO, it's better to help someone with something he can understand than to give him a black box with magic inside, unless his goal is to learn the magic now.
TIMTOWTDI.
Cameron
Understood, but teaching someone bad habits is not good, either. Best to learn the right way or it will cause problems down the line.
[edit]
Granted that a QMH might be too complicated for a beginner, but then a simple event-driven structure would've been a better choice.
It's never a good idea to peg a CPU core to just poll a button. Instead, we should be trying to help the OP understand the event structure. I looks like they already understand it enough to use dynamic events.
They're only problem was not unregistering the events. If you don't unregister, then the next registration will likely not work, which is what happened here. But the easier solution is to just not use the dynamic events since the VI Panel Close event is a default one that you do not need to register for.
@camerond wrote:
Here's an easy way to do it, using a WHILE loop, T/F Case structures and local variables.
Cameron
Ok, just looked at your example. Event structure is so much easier. And to make it even easier on you, use latching buttons. Then you don't need the locals to reset the buttons. When the button's terminal is read, the latch will reset. And I don't see where this is applicable to the OP's question about the subVI's panel not closing
