Samuel,
I've not worked with the simple OI at the code level, but your modifications sound simple enough. One suggestion - if you run the same sequence in the unmodified Simple OI, do you see the same behavior? If not, then you've somehow modified a portion of the OI that was refreshing the screen after each step. In that case, comparing the differences should help lead you to where the screen refresh was being called. Another suggestion would be to add the ProcessDrawEvents () or ProcessSystemEvents () calls in a location where it would periodically get called, such as the UI Message handling routine.
I have a feeling that when you removed the window that showed the execution of the sequence, that you may have also removed the automatic refresh of the GUI. If you don't want to see the execution of the steps. you could disable tracing into the Main Sequence callback and then hide the control instead of deleting it, or a combination of these options (hide only, leave the execution view control visable, but turn off tracing, etc). This might help you determine exactly what isn't happening in your OI that you'll need to fix.
A final suggestion would be to add a step after any Message Popups (or other steps that don't refresh the GUI properly) that forces the OI to refresh itself explicitly (ProcessDrawEvents () or ProcessSystemEvents () calls) in your Test Sequences.
Hope the above helps you figure out what's going on in your Test Executive.
-Jack
