Re: PerlApp or module change cuts print output!

The ActiveState PDK has an option to compile a "GUI Application" (or some similar name, it's been a while). If this is checked, the compiled EXE will not open a console window.

For GUI applications, it's actually kind of nice to hide the console window. For debugging, use a logger (Log::Log4Perl is nice), or use the debugger that comes with the ActiveState PDK to trace values.

<-radiant.matrix->
Larry Wall is Yoda: there is no try{} (ok, except in Perl6; way to ruin a joke, Larry! ;P)
The Code that can be seen is not the true Code
"In any sufficiently large group of people, most are idiots" - Kaa's Law

Comment on Re: PerlApp or module change cuts print output!

Replies are listed 'Best First'.
Re^2: PerlApp or module change cuts print output! by jdtoronto (Prior) on Aug 18, 2005 at 16:48 UTC
I have been using the "GUI Application" feature since day one. I dont want the user to see the console window. But it has been useful to say to them, "open a console window, then run the programme, now tell me what you see". What I have done right now is to create a new Toplevel, with a text widget. The I tie STDOUT to that I I can get the output. It is actually nicer, because I can do that without having to have the user run the app from the console. I can control the presence or otherwise of the "debug" window from within the application. jdtoronto	[reply]

Replies are listed 'Best First'.

Re^2: PerlApp or module change cuts print output!
by jdtoronto (Prior) on Aug 18, 2005 at 16:48 UTC

What I have done right now is to create a new Toplevel, with a text widget. The I tie STDOUT to that I I can get the output. It is actually nicer, because I can do that without having to have the user run the app from the console. I can control the presence or otherwise of the "debug" window from within the application.

jdtoronto

[reply]