threads and created objects

[SGaist]

@mzimmers said in threads and created objects:

I need to pursue this a bit further. So, if I have an object (my worker object) that I move to another thread, is it true that anything created within that object prior to the move "belongs" to the original thread?

If it's a QObject that is properly parented, it will move with it. Note that classes like QTcpSocket must be created in the new thread. You can however pass the descriptor like shown in the threaded QTcpSocket/Server example.

[kshegunov]

@SGaist said in threads and created objects:

If it's a QObject that is properly patented, it will move with it. Note that classes like QTcoSocket must be created in the new thread. You can however pass the descriptor like shown in the threaded QTcpSocket/Server example.

Actually a comment on that. Sockets that haven't been opened/bound can still be moved normally, however I agree it's a bad practice to depend on the actual implementation.

[mzimmers]

@SGaist said in threads and created objects:

If it's a QObject that is properly patented, it will move with it.

This is my current creation:

class Worker : public QObject
{
    Q_OBJECT
private:
    SerialPort m_serial;
...
SerialPort::SerialPort(QObject *parent) : QObject (parent)
{
...

Note that classes like QTcoSocket must be created in the new thread.

But not in the c'tor, correct? Because that is called prior to the thread move, so it would pertain to the original thread?

[SGaist]

I fixed the typo of parented (damn autocorrect...)

Yes, m_serial will not be moved.

[mzimmers]

@SGaist said in threads and created objects:

I fixed the typo of parented (damn autocorrect...

Well, while you're at it..."QTcoSocket?"

[kshegunov]

If you want the QObjects to to be moved alongside with their parent to another thread, then you must pass them the parent. No parent, no way Qt to know whether the object's supposed to be moved.

[SGaist]

@mzimmers said in threads and created objects:

@SGaist said in threads and created objects:

I fixed the typo of parented (damn autocorrect...

Well, while you're at it..."QTcoSocket?"

Argle........ Done

[mzimmers]

@kshegunov I don't know how to do that in this case. If my SerialPort object is defined:

class SerialPort : public QObject
{
    Q_OBJECT
public:
    explicit SerialPort(Worker *parent = nullptr);
...
SerialPort::SerialPort(Worker *parent) : QObject(parent)

Then how do I declare an instance of SerialPort in my worker object? If I do it like this:

    SerialPort m_serial;

Then it doesn't seem to get moved.

[SGaist]

The usual: pointer and allocate it in the constructor with a parent.

[mzimmers]

@SGaist OK, thanks. I had (incorrectly) inferred from kshegunov's post that it somehow could be done as an ordinary member variable.

[kshegunov]

@mzimmers No the inference is correct. This shall work, shan't it?

class Worker : public QObject
{
    Q_OBJECT
public:
    Worker();
private:
    SerialPort m_serial;
};

Worker::Worker()
    : m_serial(this)
{
}

[mzimmers]

@kshegunov well...yes it does. I was missing the " : m_serial(this)" clause. Thanks!