Your problem is probably derived from trying to use the GUI from two
threads. Don't do that. In your case what is probably happening is that when the forked process trys to
pop-up its message box, the Win32::GUI event loop isn't
running (since it just exited) so nothing happens.
I advise against using Win32::GUI from multiple threads because Win32::GUI stores it's data in shared (not-thread-specific) variables
(at the C level), so
race conditions could easily cause
crashes if you
do not restrain from using it in only one thread.
update:
I have neglected to give an explanation as to why perl
sticks around. I cannot think of a reason for it
to not terminate after 20 seconds, unless Win32::GUI::MessageBox
blocks, which would explain it.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|