QSignalMapper with one object being a thread (no visual object)

[anda_skoa]

You just connect the thread's signal to the dialog's slots.

I guess you have code like this somewhere in your dialog

MyThread* thread = new MyThread(this);

MyThread* thread = new MyThread(this);

To copy to clipboard, switch view to plain text mode 

so you just add

connect(thread, SIGNAL(response(QString)), this, SLOT(showResponse(QString)));

connect(thread, SIGNAL(response(QString)), this, SLOT(showResponse(QString)));

To copy to clipboard, switch view to plain text mode 

and so on.

Not sure why you would want to use a signal mapper and lose the signal arguments. Discarding the signal arguments can also be done in a normal connection.

Cheers,
_

[PeterVE]

Thank you. I did exactly that and it worked. What I had used from a Qt example was working until the upgrade. I tried to find examples online using arguments and they stated to use the signal mapper. But your suggestion is what was originally intended and does work. So thank you and have a great day!

[anda_skoa]

The signal mapper use case is if you have multiple signal sources without arguments and you want a single slot being called with arguments depending on the signal source.

E.g. a set of buttons and having the slot called with a numerical value or string depending on which button was clicked.

Cheers,
_