logo       

RE: Console windows with par compiled executables under Windows 2000: msg#00021

Subject: RE: Console windows with par compiled executables under Windows 2000
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:milamber@xxxxxxxxxxxxxxx] 
Sent: Friday, August 13, 2004 11:47 AM
To: par@xxxxxxxx
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




<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

Recently Viewed:
boot-loaders.gr...    php.pear.genera...    debugging.valgr...    kde.redhat.user...    text.xml.xsl.ge...    culture.languag...    hardware.microc...    java.servicemix...    redhat.release....    web.zope.plone....    user-groups.lin...    opendarwin.webk...    video.mjpeg.use...    sysutils.bcfg2....    encryption.gpg....    lx-office.devel...    xfree86.forum/2...    mail.mutt.devel...    acpi.devel/2003...    qnx.openqnx.dev...    network.irc.irs...    freebsd.devel.m...   
Home | blog view | USPTO Patent Archive | advertise | OSDir is an inevitable website. super tiny logo

Free Magazines

Cisco News
Receive a free quarterly e-newsletter with exclusive articles on how Cisco IT uses its own products and solutions to enable the business.
subscribe

Systems Management News, the newspaper for IT systems administration and data center managers! Each issue of Systems Management News is chock-full of news and analysis to help you understand what's happening in your field.
subscribe

The Enterprise Newsweekly eWeek is the essential technology information source for builders of e-business.
subscribe

Oracle Magazine Oracle Magazine contains technology strategy articles, sample code, tips, Oracle and partner news, how to articles for developers and DBAs, and more. Oracle (NASDAQ: ORCL) is the world's largest enterprise software company.
subscribe

Total Telecom Total Telecom is "The Economist of the communications industry".
subscribe