Qt bug? Signal emitted once, slot called multiple times

[wysota]

You can't prove anything without showing how you create your socket object. I still claim the whole tree of objects is moved to the new thread. If you say something about pointers then you probably don't really understand what thread affinity in Qt is.

[MattPhillips]

wysota, it was

class MyObject : public QObject
{
    Q_OBJECT
 
    public:
        MyObject(...);
 
    ...
 
        QLocalSocket* sock;
};
 
MyObject::MyObject(...)
{
    sock = new QLocalSocket();
}

class MyObject : public QObject
{
    Q_OBJECT

    public:
        MyObject(...);

    ...

        QLocalSocket* sock;
};

MyObject::MyObject(...)
{
    sock = new QLocalSocket();
}

To copy to clipboard, switch view to plain text mode 

But, after reading your comment I tried it with

sock = new QLocalSocket(this);

and indeed, like you said, sock *did* pick up the thread affinity of the parent. So it looks like the ConnectSignal workaround I came up with earlier wasn't necessary. So, thanks indeed for the insight and better solution. But it's still the case that *unless* you make a class member the child of the class instance, then member thread affinity is not changed when class affinity is, no?

Matt

[wysota]

Of course the member affinity is not changed. Why would it be? Besides, the socket object is not a member of your class. Only a pointer to a socket object is and that does not have thread affinity.