[Kst] piping into kst doesn't work when the data aren't immediately available (cvs)

George Staikos staikos at kde.org
Wed Aug 23 23:44:34 CEST 2006

On Wednesday 23 August 2006 11:00, Melchior FRANZ wrote:
> * George Staikos -- Wednesday 23 August 2006 16:43:
> >   I don't see any comment in your original message about trying it
> > exactly like that.  I'll assume you did.  Can you prepare a simple
> > testcase for us to reproduce the problem?
> Hey, between the lines! :-)
> OK, you are right, sorry. Just thought that my insistence on this being
> because the data aren't immediately available (subject!) implied that it
> worked *when* they were immediately available (such as via cat or any
> other app that doesn't take two minutes to spit out data).
> Attached is the test case. Run as
>   $ ./nogo 0|kst -y 1 -n 500 stdin       # 0 seconds delay -> works
>   $ ./nogo 10|kst -y 1 -n 500 stdin      # 10 seconds delay -> doesn't work

  Thanks for the testcase.  I see the problem and have a patch coming up.  
However it needs some thorough testing and I may back it out again.  The 
patch tells Kst to keep vectors loaded from the commandline around even if 
they're not found in the file because they might show up later.  I think this 
is OK behavior, but I want to be sure that it doesn't cause any problems with 
traditional usage.

George Staikos
KDE Developer				http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/

More information about the Kst mailing list