Coincidentally, I just implemented this very thing with Wx just last week.

Just use IPC::Run to fork your runProcess1() and return control to Wx::MainLoop. To effect a pause rather than a stop, you'll probably want to use signals (IPC::Run::signal) rather than IPC::Run::kill_kill to terminate the detached process. Maintaining state "is left as an exercise to the reader" :-)

Because your runProcess1() will be detached and the Wx GUI functional, you'll want to disable any GUI elements that could do things that might change the environment of the background process in an undesirable way.

Wow, two plugs for IPC::Run in one day... and I don't even know the author!

In reply to Re: wxPerl Event Handling/GUI process control by gloryhack
in thread wxPerl Event Handling/GUI process control by sush

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.