> "This is certainly occuring because of the "Always on Top" selection. However, there is one
> option you have here. You could try using Dynamic Events. They're new to LabVIEW 7.0.
> You can actually unregister a particular event (tab changed) and have it only trigger when you
> want. For instance, you could unregister this right before the cancel window comes up. Then, if
> the user clicks the tabs, since this event is unregistered, they will not be tallied. Then, when you
> get back to that window, there will be no events stored up so nothing should happen."
Comment above was posted by JRA on the inadvertant second posting by the same name. It sounds like the solution to my problem although I don't have version 7 ye
t to try it with.
> it isn't clear why you are moving from modal to floating.
The reason I am changing the dialog from modal to floating is because there are two windows the program normally has open, one of which I want to work, the other which I want disabled. A modal box will not allow the user to access the main user interface window, but it will also not allow the user to access the command window. The main window needs to be completely disabled while the command window will allow the user to select items from the menu and execute code associated with those items. When the main window executing a subvi that is always on top, it appears to be working in the manner I would like it to because the rest of the user interface is not accessible while the command menu is, however, unknown to the user, any events that take place in the main window and don't appear to be doing anything are actually being queued--they are processed in full once the execution of the subvi is complet
e. I hope that explains things a little better--it's kind of a confusing problem.
Thanks for your post... I'm guessing I'm going to have to wait for the purchase paperwork to go through for version 7.