Re: Re: Perl TK on Win32

I know from my TCL/TK days that this type of solution can destroy a decent program. Just the resulting disk I/O does not make this worthwhile. (I tried this once, even with a ramdisk and my program took longer by a magnitude of 4.) At the very least I would look at working with a MySQL database and store the info in there for better retrieval. By the same token, I could run the GUI separate from the rest of the program and then run the daemon as a console application that outputs text files to be read by the GUI.

Or even: `start /m rsh $server dir > ${server}.txt` Also, these windows go away in a flash, but each iteration of the mainloop calls 6 rsh'es for 6 different servers, and you get this obnoxious flash of console windows. And as we add more servers to check, this could get really ugly. So if it comes down to needing to somehow run the program from the console, WTF am I fartin' about with Tk?

I'm starting to get the impression that this "cannot be done" and I also feel that I am about to get the "It's Window's fault" post. But this is from TCL/TK code that worked (with a few signal trapping incidents), and had none of the console problems. Last night I ported it over to VB and ran it without too many problems. (I suck at VB)

Before you warm my toes with flames, I don't mean this to say that one is better, and I know comparing the different langs is like comparing apples and oranges. The point I am making is that if there is not a mechanism to achieve this in Perl, is there a wish list? It seems that this is something that I have seen alot of people struggle with, and nobody has a solution.

EDITED Also, I tried using the Win32::Process to write out to tempfiles, and this only suppreses the rsh Windows if the perl script is run this way. (In essence starting it from a console.) Again this begs the question, why am I using TK?

I'll keep working on this, and if I can find a way, I'll make a module out of it. But this is something that I think should be a core feature. use Tk::Exec; Tkexec("rsh $server dir", $dir); or something like that.

And to respond to a later post, I used the wperl.exe, same result.

Comment on Re: Re: Perl TK on Win32 Select or Download Code

Replies are listed 'Best First'.
Re: Re: Re: Perl TK on Win32 by jplindstrom (Monsignor) on May 12, 2001 at 02:40 UTC
Or even: `start /m rsh $server dir > ${server}.txt` Also, these windows go away in a flash, but each iteration of the mainloop calls 6 rsh'es for 6 different servers, and you get this obnoxious flash of console windows. Did you try this? `start /b yourprogram` start /? says: B -- Start application without creating a new window. The application has ^C handling ignored. Unless the application enables ^C processing, ^Break is the only way to interrupt the application Run this, then remove the /b option and the windows start flashing again. `for my $i (0..10) { print "\nStarting $i\n"; system( qq{start /b perl -e "print 'program $i'";} ); }` [download] /J	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re: Re: Re: Perl TK on Win32
by jplindstrom (Monsignor) on May 12, 2001 at 02:40 UTC

Did you try this?

start /b yourprogram

start /? says:

B -- Start application without creating a new window. The application has ^C handling ignored. Unless the application enables ^C processing, ^Break is the only way to interrupt the application

for my $i (0..10) {
    print "\nStarting $i\n";
    system( qq{start /b perl -e "print 'program $i'";} );
    }
[download]

[reply]
[d/l]
[select]