Thanks for the replies, the open is working properly on the background.
I'm able to keep working while the $cmd is running.
The $reg_out is output to a text gadget. If you think the open cmd is the issue, how should I fix it? I want to run a CMD on the background, grep the output to be paste on a text gadget on the main process gui
This is the code of the fileevent, I'm closing the descriptor once the program is done
sub fill_text_widget {
my $block = shift;
my $numb = shift;
my $widget = $Reg_r{$block}{$numb}{'Txt'};
my $out_rep = $Reg_r{$block}{$numb}{'OutP'};
if (eof($out_rep))
{
$widget->fileevent($out_rep,"readable", undef);
close $Reg_r{$block}{$numb}{'OutP'};
print "Got EOF\n" if ($DBG);
$Reg_r{$block}{$numb}{'IsRun'} =0;
&AddReRun($block, $numb);
return;
}
$_ = <$out_rep>;
$widget->insert('end', $_);
$widget->yview('end');
}
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|