KDE/kdelibs/kdeprint

Andreas Pakulat apaku at gmx.de
Thu Jun 28 09:39:23 BST 2007


On 28.06.07 10:12:44, Simon Hausmann wrote:
> On Friday 15 June 2007 18:57:54 Andreas Pakulat wrote:
> > WTF! Thats not only not obvious but clearly a problem. How should a user
> > of QProcess be able to read error and output separately without loosing
> > data or having to store 2 buffers. Thats just insane, where's the "Code
> > less, Create more" here?
> >
> > Any of our TT contacts want to speak up? Seriously the QProcess API is
> > really hard to use, the documentation is lacking, thats not what I'm
> > used to from Qt. And we're already at Qt4.3 here, its not like this
> > class is new or anything.
> 
> I don't think is an API problem, it is plain data loss bug. We've fixed it for 
> Qt 4.3.1 and I've applied the patch to qt-copy. Switching read channels no 
> more looses data. Just use it as you'd expect it to work, the 
> readAllStandard(Output|Error) as well as the canReadLine/readLine while loop 
> should work just fine now.
 
Thanks. /me hopes that Qt4.3.1 is released and available in
distributions when KDE 4.0 comes out :)

Andreas

-- 
You will be held hostage by a radical group.




More information about the kde-core-devel mailing list