Bug in KProcess?

[Waldo Bastian]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 02 September 2002 02:25 pm, Sebastian Trüg wrote:
> > You pass "NoRead" so you have to do the reading yourself and update the
>
> length
>
> > according to what read() returns.
> >
> > I guess you not want to pass NoRead and instead let KProcess do the
>
> reading
>
> > for you. You must connect to the other receivedStdout() signal in that
>
> case.
>
> > Cheers,
> > Waldo
>
> Damn it. I'm such an idiot!
> No, I really want to do the reading on my own because I need to have
> influence on when the data is read. Actually I'm piping the data on stdout
> into another process and have to wait until it has been written.
> But what you write sounds like I have to read the data in the slot
> connected to the stdout-signal. Is that right? 

Yes.

> Or is there any possibility
> that KProcess suspends processing stdout until I read it?

call suspend() :-) (and resume() to resume)

Cheers,
Waldo
- -- 
bastian at kde.org  |   SuSE Labs KDE Developer  |  bastian at suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9c+8CN4pvrENfboIRAommAJ471qifNMRuiMaEcLX3szIpllCFYwCgnNLb
sGlGWMi/5iKLc7athCsmNmg=
=chr9
-----END PGP SIGNATURE-----