user interface blocking

[serialdaq]

hi;

I've developed a test in cvi but for comparing and reporting options of test stand,I've decided to run my .c files as a .dll in test stand.(I have more than  500 measurement,and its so harder to write code for comparing and reporting these results)

Because my measurement routines takes long time,I created a status text box to inform operator about the status of the test and not to be anxious if every thing about the test is all right or not.I load the panel with Load PanelEx() first two steps no problem,because test equipment initilization and some port tests does not cause any prblem.But after this the following sequence steps containes routines which sets more than 5 equipment and get more than 100 measurements.And there is no way to divide the step to smaller pieces.And problems appears here.The user interface blocks if you activate another menu from any other application line cvi userinterface,outlook menu and minimize them the piece of previous interface remains on my execution user interface.The status text box messages continues to appear but led identification and command buttons all hide under the blocked piece.I do not use "runuserinterface" command at the first step.Because if I Run it ,the test stand sequence that I've created does not run ,stands still..

I only have a quit command button to quit user interface.Because I don't want the user interface disappear itself , unless the operator want.When "QUIT" button is pressed the userinterface disappears and report is generated.But if the blocked pieces of the other apllications(outlook, cvi) hides this button.I can't press it and can nopt complete my execution.I want to remind that at every step beginning I've added "Displayuserinterface" but it does not help me to get whole user interface.

I now its so hard to understand, I can send you screen shots to make it clear...

thanks...

[Al.B]

Hi Serialdaq,

If I understand correctly, the behavior you are seeing is that the operator interface is not refreshing when another window is maximized and minimized, and the OI window displays an image of the last window instead of the actual interface.  This behavior may be occurring from one of two reasons: The first is that either your code module or the text box is using the entire processor due to a lack of any programmed waits.  Make sure that your code module is not executing any loops without some sort of wait to ensure that the processor is given time to complete other tasks such as updating the OI.  The second possibility is that you may be launching the status text box in the same execution as the main OI, which means that the OI is waiting for the dialog box to finish executing before it updates.  This can be fixed by calling the text box in a subsequence, with the call subsequence step set to run reentrantly.  More information on how to do this can be found in the following KnowledgeBase Article:

How Can I Execute a TestStand Sequence Asynchronously?

Hope this helps!