At 13:43 2005-02-16, Bret Swedeen wrote:
>The first problem I have is that if the collection takes too long, parts
>application screen turn gray (basic default background color) and blank
>out any of
>the older data until the data collection is complete and the screen is
>question here is how do I stop this gray-screen thing from happening? Do
>I need to
>spin this data collection sub procedure off as a separate thread?
If you can call Win32::GUI::DoEvents from within this collection procedure,
that would take care of the problem.
If not, you should take a look at my suggestion at
on how to do this in a separate worker thread.
>The second problem is that during the same long data collection stage the
>will sometimes flash to a command window and then back. When this happens
>returning application screen is sometimes gray (see above problem). Now, the
>important thing to note is that this problem only happens when I launch the
>application using wperl.exe. If I start with perl.exe the command window
>is in the
>background and hence no flashing occurs; however, the above gray-screen thing
I guess you run a system("somecommand"). You could run it as system("start
/MIN /WAIT somecommand") to have it run minimized to the task bar. Maybe /B
could also be interesting. Run "start /?" from a cmd shell to see all the
-------- ------ ---- --- -- -- -- - - - - -
Johan Lindström Sourcerer @ Boss Casinos johanl AT DarSerMan.com
Latest bookmark: "TCP Connection Passing"