Undesirable application behaviour during "Shell.runAndWait"

[GKFC]

Hi,

I have an installer application that is running fullscreen with graphics and animations.

At a certain point, I use Shell.runAndWait to launch a couple of other child applications. These child applications in turn launch a number of boxes around the screen (which I cannot control).

Unfortunately, when each of these child applications run / launch their boxes they leave a horrible white box over my main application when they have finished. Almost like it has "cut" a portion of my application out.

As soon as Shell.runAndWait has finished my application returns to normal, but for the duration of the child applications running the screen looks really ugly....

I can't use Shell.run as I need to wait for each of the child applications to finish before launching the next one.

Any ideas?

Cheers,

G.

[GKFC]

I have also tried using Shell.runAndWait(child application.exe, 0) to not show the application. Unfortunately, since the child application launches a number of other boxes, it only hides the FIRST box and shows the rest.... all of which "cut" a portion out of my main application....

???

[SWFKit]

Please call the "processMsg" method after the call of "runAndWait". The processMsg method will redraw the main window.

Shell.runAndWait(app1);
if (!processMsg()) return;
Shell.runAndWait(app2);
if (!processMsg()) return;
Shell.runAndWait(app3);

[GKFC]

Well, it "almost" works....

When the child application first launches, the processMsg code successfully redraws my main application.

However, after the last window of the child application closes there is about a 5 second wait before the actual child process finishes and returns a result to SWFKit. For these 5 or so seconds my main application is cut out again....

I tried putting a loop running in the background that is called every half a second to execute the code "if (!processMsg()) return;" but to no avail....

???

Any enhancements or other ideas would be appreciated....

Cheers,

G.

[SWFKit]

5 seconds waiting after closing the last child process?

1. If the child process takes 5 seconds to exit after the "x" button has been clicked and its main window is disappeared, there is no way to avoid the window cutting.

2. After the last "Shell.runAndWait" call, there are some other codes to run. I think it's the most possible case. You can insert some processMsg calls in it.

You can launch the last app separately and get its closing time using the "Task Manager".