Bug in KProcess?
bastian at kde.org
Tue Sep 3 00:06:38 BST 2002
-----BEGIN PGP SIGNED MESSAGE-----
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
> > according to what read() returns.
> > I guess you not want to pass NoRead and instead let KProcess do the
> > for you. You must connect to the other receivedStdout() signal in that
> > 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?
> Or is there any possibility
> that KProcess suspends processing stdout until I read it?
call suspend() :-) (and resume() to resume)
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
-----END PGP SIGNATURE-----
More information about the kde-core-devel