Thanks! I searched google, but must have not used the right words.

As a side note you must use Win32::SetChildShowWindow(0) in each thread
that creates child processes.

Thanks!

james evans

Jesse Schoch said:
> Google is your friend
>
> http://216.239.39.104/search?q=cache:WrJ3hT5UyJgJ:aspn.activestate.com/ASPN/
> Mail/Message/perl-win32-users/2127463+win32::Process+command+window&hl=en
>
> Thanks Jan,
>
> That did it!  Why does system() do this when the script is GUI compiled?
>
> Just curious.
>
> Dax
>
> *********** REPLY SEPARATOR  ***********
>
> On 7/25/2004 at 12:42 PM Jan Dubois wrote:
>
>> On Sun, 25 Jul 2004, Dax T. Games wrote:
>> > I tried to search the archives on this but i am getting errors when I
>> > try submit the search.
>> >
>> > How can I start a process with Win32::Process then wait for that
>> > process to close before continuing execution of my perl code.
>> >
>> > system() does not work in my case because it is a GUI compiled perl
>> > script and system() creates a new command window when called.
>>
>> Try calling
>>
>>     Win32::SetChildShowWindow(0);
>>
>> before calling system() to get rid of the additional shell window.
>>
>> Cheers,
>> -Jan
>
>
> -----Original Message-----
> From: James Evans [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 13, 2004 11:47 AM
> To: [EMAIL PROTECTED]
> Subject: Console windows with par compiled executables under Windows 2000
>
> Hi,
>
> I'm using par to compile my wxPerl based app on Windows 2000 under
> ActiveState perl 5.8.3 build 809 and PAR-0.85. At various places in my
> application I call a command line based app (using qx()) and process the
> output. When I run 'perl script.pl' everything works as expected. After I
> compile my app with 'pp --gui -l \perl\site\lib\auto\Wx\wxmsw24.dll -o
> script.exe script.pl' every time I use qx A console window pops up on the
> screen for the duration of the command. using system() has the same
> problem.
> If I don't use --gui I get a console window at the beginning of the app
> that
> stays around for the duration of my script (as expected) but no per qx()
> console window.
>
> Why the difference in behavior? I'd expect qx to behave exactly the same
> when run under perl as when the resulting exe is run. This really impacts
> the polish of my application and would like to find some way to avoid
> this.
> I can't find anything in the archives about this but have a hard time
> believing that no one else has ever had problems with this.
>
> Thanks for your help and hard work creating PAR. I love being able to
> create
> native executables in my favorite language!
>
> james evans
>

Reply via email to