I have a program that reads a list of codes and sequentially launches corresponding .bat files using the System.Diagnostics.Process.Start method and then does a procID.waitforexit() before launching the next .bat file in sequence.
When the .Start method opens the command prompt window and launches the .bat file, the window partially covers the main program's window. Moving the newly opened window does not cause the main program to repaint the window thereby leaving blank spaces denying the user from seeing the main program's status messages. I'm pretty certain that the waitforexit() function is put the main program into an idle state to the point where it will not process any screen painting commands.
Is there anyway to:
a) control the position of the new process's window, or,
b) loop around the waitforexit() giving it a 500 millisecond pause time and call a DoEvents() inside the loop so that the program can repaint its status messages?
Ideally I'd like to do both, but I will settle for only (b).
Thanks in advance!
The Not-So-Big Cheese