Open GoogleCodeExporter opened 9 years ago
I had the same problem. The solution is: separate GUI and QextSerialPort
communication to different Threads. This will also improve the performance of
the serial port functionality.
Original comment by maikelme...@googlemail.com
on 29 Apr 2013 at 6:45
I notice that QT's QSerialPort will fix this issue in their up-and-coming 5.5
release
https://bugreports.qt.io/browse/QTBUG-34946
https://codereview.qt-project.org/#/c/71871/
It says the the above pages to use the QWinOverlappedIoNotifier instead of the
QWinEventNotifier.
QExtSerialPort includes <QtCore/QWinEventNotifier> in qextserialport_win.cpp.
If I upgrade my QT to 5.5, will this stream issue be fixed? Or, will my
Qextserialport code need changed?
I know having separate threads will fix any issues, but due to the length of
code and my lack of experience, this maybe hard for me to implement.
Original comment by patrick....@gmail.com
on 16 Jun 2015 at 8:40
Original issue reported on code.google.com by
tim.ess...@googlemail.com
on 8 Aug 2012 at 9:25