Prev: v 8.5.5 basic programs
Next: A problem of oratcl orabindexec cmd
From: Alexandre Ferrieux on 11 Dec 2008 05:33
On Dec 11, 2:36 am, Richard Owlett <rowl...(a)atlascomm.net> wrote:
> David Gravereaux wrote:
> > Richard Owlett wrote:
>
> >>It didn't work :(
> >>Gnuplot opened, but nothing seemed to go to the opened window.
>
> > Look in the bin directory.  IIRC, there is another executable
> > specifically for using with pipes.
>
> I assume you are referring to wgnuplot_pipes.exe .
> Didn't work either :(

Well, did you flush your [puts] ?
Alternatively you can [fconfigure -buffering line].

-Alex
From: Richard Owlett on 11 Dec 2008 06:54
Alexandre Ferrieux wrote:

> On Dec 11, 2:36 am, Richard Owlett <rowl...(a)atlascomm.net> wrote:
>
>>David Gravereaux wrote:
>>
>>>Richard Owlett wrote:
>>
>>>>It didn't work :(
>>>>Gnuplot opened, but nothing seemed to go to the opened window.
>>
>>>Look in the bin directory. IIRC, there is another executable
>>>specifically for using with pipes.
>>
>>I assume you are referring to wgnuplot_pipes.exe .
>>Didn't work either :(
>
>
> Well, did you flush your [puts] ?

Yes. And being from the era when NULLs were important for time delays
I did it line by line -- 10 CPS Teletypes teach lots of tricks

> Alternatively you can [fconfigure -buffering line].

Will try that.

Does anyone have known working sample/test case?

If anyone has any doubts, I _AM_ a Tcl newbie ;/

From: Uwe Klein on 11 Dec 2008 07:24

You want to plot to the screen, right?

two lines on one plot?
or
1 line on two different plots?

your code from further up would
do two different plots in fast succession

puts $plotfp " plot 'C:dataset1.dat' using 1:3"
flush $plotpf ;# first plot

puts $plotfp " plot 'C:dataset2.dat' using 2:3"
flush $plotfp ;# second plot

# one plot, two lines
puts $plotfp " plot 'C:dataset1.dat' using 1:3, '' using 2:3"

# dont:
# Close the pipe.
close $plotfp;# sends an EOF

I know not much about windows.
If you send commands to gnuplot
and then immediately close the input
you may not see much more than a flashed window
( even that may not be sure thing )

uwe

From: Alexandre Ferrieux on 11 Dec 2008 09:20
On Dec 11, 1:24 pm, Uwe Klein <uwe_klein_habertw...(a)t-online.de>
wrote:
>
> If you send commands to gnuplot
> and then immediately close the input
> you may not see much more than a flashed window
> ( even that may not be sure thing )

At least in the unix version of gnuplot, there's a -persist option to
let the display window linger after EOF on the pipe/tty input. It then
just stays there, servicing resize requests (zooming the graph), until
the wm shuts it down.

-Alex
From: Uwe Klein on 11 Dec 2008 09:54
Alexandre Ferrieux wrote:
> On Dec 11, 1:24 pm, Uwe Klein <uwe_klein_habertw...(a)t-online.de>
> wrote:
>
>>If you send commands to gnuplot
>>and then immediately close the input
>>you may not see much more than a flashed window
>>( even that may not be sure thing )
>
>
> At least in the unix version of gnuplot, there's a -persist option to
> let the display window linger after EOF on the pipe/tty input. It then
> just stays there, servicing resize requests (zooming the graph), until
> the wm shuts it down.

Yes, though that has its own idiosyncrasies
and you have to tell gnuplot to do that explicitly.

Having gnuplot via expect/pipe do repeated updates
completely ruins your pastebuffer.

uwe

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: v 8.5.5 basic programs
Next: A problem of oratcl orabindexec cmd