On Thu, Apr 4, 2019 at 6:42 PM Jérôme Godbout wrote:
> You jus did the same loop into your slot, the function I did made can be
> called as slot to the connect you just told, I agree the
> serial_port->waitForReadyRead(5); is not necessary, just often the
> transmission have partial or bunch of d
On Thu, Apr 4, 2019 at 9:37 PM wrote:
> Try testing them with a million+ row table.
>
Been there, done that. Be a lamb and stop with the nonsense. I'm sure you
run every file operation in a dedicated thread, 'cause you'd *"never ever
ever do I/O in the main GUI thread of a Qt application" ...*
W
Yea, I'm going to have to agree with Denis over Roland. In general it's not good to do synchronous operations (expecially I/O) in the main thread, but Qt I/O is mostly* asyc.
*caveat: data reading/writng is async, but things like QDir::mkDir() are sync. So if you're on a slow 5400RPM disk with
> Never ever ever do I/O in the main GUI thread of a Qt application.
Why not? It is an asynchronous. You can do I/O in a main thread, but handle
data in a separate thread (e.g. to parse it). Of course, it depends on the
used communication protocol and etc.
A main limitation is that on Windows all
Quoting interest-requ...@qt-project.org:
I think the point is that there's little reason to poll the serial port if
you can react to the event. Exactly what you'd do if you had a network
socket. Qt already does the heavy lifting for you, so you only need to
react to the signal and read as much
