I have a truly unusual GUI phenomenon using a sub-panel in a sub-panel (in LabVIEW 7, obviously ;-).
Basically, my main VI has a dynamically loaded switch driver whose configuration window is loaded as a sub-panel into the main VI. In the switch driver's configuration window, the user can select a function driver which is also called dynamically with its own configuration window as a sub-panel of the switch driver.
The funny thing is that while in the switch driver everything is fine, in the function panel's window it takes many clicks to do anything (as if the computer were missing mouse clicks). If I want to select an item from a pop-up menu, I have to click 3 or 4 times until it pops up. The same thing happens with trying to enter values in a numeric control.
Now, normally when I see the computer apparently freezing up or reacting sluggishly to user input, it's been because there were no waits in the GUI loops. Yet I've used the Wait MS function in both the switch driver and function driver (values of 10 and 100 ms, respectively), but it doesn't seem to have had an effect.
Furthermore, I've run with the light bulb on in the function driver and it's not really doing anything (all Cases are False)- it's just looping through (when the light bulb is on, the controls react normally).
It's all very strange. Again, all the controls in the Switch driver respond very quickly (pop-up menus pop up when clicked on, numbers can be entered with ease). It's just the function driver's window which seems to be "missing" user clicks.
Any ideas?
Thanks (in advance), E. Blasberg iDAQ Solutions Ltd
P.S.- All VIs have Normal priority and run in the same thread... (Windows XP Pro on a Pentium IV 2.0GHz machine, in case that matters). I do use dual monitors, but the program is running on the "main" monitor (for whatever that's worth).
This just in: setting the Wait MS to 500 (0.5 sec) helped significantly. However, the question remains: why should this be necessary when elsewhere it isn't?
