The event handling is divided amongst multiple loops for the sake of encapsulating the related code - in the actual program, there are lots of controls on each tab and lots of events to handle. Lumping all the events together in a single event structure makes the code less readable then I would like.
The two tabs are supposed to behave like entirely separate dialogs - because in my situation it's not desirable to have to load another VI. (This tabbed dialog resides in the subpanel of a main frame. I don't want to programmatically load a different sub-panel, as these two tabs are enough alike to warrant being grouped together). Plus, each tab has it's own intialization and shut-down sequence - just like a top-level VI might have, which further complicates the one event structure approach. Thanks for trying to help me out, and I appreciate the code snippet, but it wasn't quite the reply I was looking for. Maybe I should have more clearly stated my request. Any ideas as to the cause of the freezing? To my (perhaps untrained) eyes, there seems to be no logic problems in my original diagram. This is what I see - the inner loop terminates, and the tab control is reset. The front panel is locked until the event completes, and as soon as the panel unlocks, the tabs should be switched so there is no way that the button should register the double-click. I was wondering if I could get some etails as to the true cause of the freeze. If anyone had some more information about tab controls, etc., it would be appreciated.
