@RolandHughes

About what kind of class are you talking? If this class of addon QtSerialPort, then:

...which will be included as part of Qt 5 according to the Web site.
This is not quite true. This class is an addon, but is not part of Qt! And most likely will not be as part of Qt, because it is the development of
custom developers, who do not have the time and resources to prepare and test the addon.

At the moment, in fact, the development is supported and is active only one developer.

The examples are all kind of worthless.
Wow? O_o What makes you think that they are useless?

This Open Source project, no one is obliged to write to you. Write yourself a useful example in
your opinion, and then I will maybe I add your example to trunk.

The documentation says the SerialPort class is thread safe, yet, SerialPort.h deliberately disables a copy constructor which makes it very difficult to do signalling.
Where is it written that it is "thread safe"? It is not so.

I have found many cheating examples which call waitForReadyRead() instead of doing it right.
Where cheating? In BlockingMaster/BlockingSlave? O_o

Looking actual compiling example of SerialPort class using signals and slots within a thread which is NOT the GUI thread.
In addition to the Terminal example, there are other examples of the use of signals / slots without using Threads.
Look here: https://codereview.qt-project.org/#change,41981

But they have not yet added to trunk.


Therefore, your conclusions are absolutely baseless and unconstructive.