At 13:43 2005-02-16, Bret Swedeen wrote:
The first problem I have is that if the collection takes too long, parts of the 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 repainted. The 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
<http://sourceforge.net/mailarchive/forum.php?thread_id=6472247&forum_id=3220>
on how to do this in a separate worker thread.


The second problem is that during the same long data collection stage the screen will sometimes flash to a command window and then back. When this happens the
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
still happens.

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 options.


/J

-------- ------ ---- --- -- --  --  -     -     -        -          -
Johan Lindström    Sourcerer @ Boss Casinos   johanl AT DarSerMan.com

Latest bookmark: "TCP Connection Passing"
http://tcpcp.sourceforge.net/
dmoz: /Computers/Programming/Languages/JavaScript/ 12


Reply via email to