Strange Freeze-Up w/Event Structure

[DL84]

Dang thought I was onto something..i set the properties during runtime within the subvi to open front panel when called, and close after completion...but didn't in the subvi node setup from within its caller vi.

Tried that but no change.

Also verified it doesn't keep running by running the subVI alone.  After clicking cancel the vi outputs and ends properly. (Run arrow switches back to run instead of running)  So its confirmed that the access VI does complete gracefully.....

[DL84]

Figured it out.

I feel stupid lol...even though the code never entered those other test situations unless told to do so, there was an unused event condition inside both of those tests that made use of that exit variable from back when I first started coding this application.  I had changed how I wanted it structured but forgot to remove those - so when I hit that exit, those blank events happened but they didn't compensate.  Program flow didn't have to allow those parts to be accessed, since it was event controlled it just happened, and since it was in the same VI they weren't isolated.

Doh.  So it was hung up in another part of the program that wasn't supposed to exist lol.

Thanks for the help!

[altenbach]

'glad you figured it out. :) Things like that are often Layer 8 issues. 😄