Rob's work sounds cool!
About the threads exiting issue this is what the manual page says:
-------------
WARNINGS
A thread exited while %d other threads were still running
A thread (not necessarily the main thread) exited while there were still
other threads running. Usually it's a good idea to first collect the return
values of the created threads by joining them, and only then exit from the
main thread.
-------------
In my experience the detach method seems to be experimental. The main thread
exiting before other threads causes the entire script to exit. Also a thread
using the Crypt::SSLeay or Net::SSLeay module, causes weird crashes if
detached, but works "reasonably" okay if not detached. Hopefully this will
be fixed in a later version of Perl and/or SSL modules!
Cheers,
Emmanuel
p.s. Wishing you all a great year ahead.
----- Original Message -----
From: "Jeremy White" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<perl-win32-gui-users@lists.sourceforge.net>
Sent: Friday, December 30, 2005 8:31 PM
Subject: RE: [perl-win32-gui-users] PerlApp issue
One thing I noticed in my program, that also occurs when I run your
example,
is that I get a message complaining that "A thread exited while 6 threads
were running" if the main window is exited first. I thought the detach()
method was supposed to prevent that. I seem to remember that when you
actually do a join(), as suggested in the documentation, there are other
problems. Do you also see this? Do you know what is going wrong?
Yes I get this too. I think that the message is mainly a warning, and in
most simple cases can be ignored. The correct approach is for all child
threads to terminate smoothly, under the control of the main thread before
the main thread itself terminates.
Cheers,
jez.
