Hello Community, I'm wondering if there is a logical explanation for the following behavior: My Main VI has a button to change a counter and a subpanel displaying another VI (test). The test VI has a button to change a different counter inside itself and also a stop button Both VIs use a separate event structure to handle the button presses, of course each VI handles its own buttons only. When I start my main VI it also starts the Test VI in the subpanel so I can change both counters with the buttons. Now comes the problem: if I stop the VI in the test VI by pressing its stop button then it finishes the execution, but if I press its counter button (note the VI finished already) then it locks my front panel and from that point my main VI front panel does not respond anymore. So a VI which is not running can somehow still register events. Interesting, but more to come. If I uncheck the "lock panel" checkbox for the events in the test vi and keep pressing the counter button in my stopped test vi and then restart the test VI in the subpanel then the counter value changes. This may sound confusing, but I have attached a project. Steps to reproduce: Open the main VI (make sure the test VI is not open, otherwise an error occurs) Run the main VI Press the counter button in the Subpanel couple times and note the value Press the counter in the main VI just to see that it works Press the stop button in the subpanel. The LED stops blinking Press the counter in the main VI just to see that it still works Keep pressing the button in the subpanel couple times Press the stop button in the main VI Tada! The VI in the subpanel restarts and the counter will have a higher value than it has before. The VI in the subpanel was not running but the event structure still registered the clicks and when the VI restarted the events were fired. If you open the test VI and check the "Lock panel" option in the event properties then everything locks at step (6). I'm not sure if this is a bug or a feature, but certainly looks a very odd behavior. I hope my explanation was clear enough, let me know your thoughts. The project was written in LV2015. thx.

LabVIEW

… and this is why you should Remove VI from subpanel and close ref's when they're not active. 🙂

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems

Message 11 of 11

(261 Views)