> Hi Thiago, Kuba,
>
>
>> It should support the same waitForBytesWritten() and waitForReadyRead() that
>> QAbstractSocket and QProcess have. Those are blocking.
>Yes, QSerialPort does it (at least tries to do). :)
>>Let's make sure we distinguish blocking from buffered. It's quite ok for
>>QSeri
>Hi.
>
Hi again,
Disclaimer. I don't work for Digia and I have never worked for Digia. I did
work for Trolltech and Nokia though.
>I once again fluently look source codes of Qt and I see that the only one
>I/O class which supports a buffered mode is QTcpSocket (i.e.
>QAbstractSocket in buffere
Hi,
I'm not sure I understand your question so I'll reply according to what I
understood.
QIODevice is a generic interface and as such has to provide an interface that
works well with different ways of doing things. What seems to confuse you is
the possibility of doing buffered communications
(sorry for jumping in the middle of the discussion)
>Quoting style guides that apply for applications can by definition not
>contain reasoning for library writers. Apps live in their own little
>dream world and can play with the compiler flags anyway they wish. They
>only target one App, after
