> On Wed, 18 Jun 2008, Charles Alderman wrote:
> > I've had some luck doing this using fork() and a pipe to communicate
> > between the (pseudo) processes. On Win32, fork is emulated using perl
> > threads. So it's basically the same thing. I haven't tested this on
> > Perl 5.10 yet, but I've ha
- Original Message -
From: Jan Dubois <[EMAIL PROTECTED]>
Sent: Wed, 18 Jun 2008 10:58:28 -0700
Re: RE: [perl-win32-gui-users] Avoid the appearance of a "frozen" window
> You are not really supposed to use GUI handles from a thread that doesn't
> own them (the one that has created them).
On Wed, 18 Jun 2008, Charles Alderman wrote:
> I've had some luck doing this using fork() and a pipe to communicate
> between the (pseudo) processes. On Win32, fork is emulated using perl
> threads. So it's basically the same thing. I haven't tested this on
> Perl 5.10 yet, but I've had a gui appli
I've had some luck doing this using fork() and a pipe to communicate
between the (pseudo) processes. On Win32, fork is emulated using perl
threads. So it's basically the same thing. I haven't tested this on
Perl 5.10 yet, but I've had a gui application built this way running
and in use f
Hi,
If you are doing the processing in a loop, you can call DoEvents which will
unfreeze the window and process all events currently in the queue. This
approach would only work if the call to DoEvents happens frequently enough
while you are processing. The alternative approach is to use thread
5 matches
Mail list logo
