Yes, I should have written updateView(const QueryResult&), but I thought it would be pretty obvious that the signal would need to transport the data as its argument.
In what way?
Why on earth would you need a signal mapper?
You would not use a signal mapper when you can use a trivial signal/slot connection between two objects.
Heavly for how many seconds?
The first Google hit on signal/slots is the Qt documentation on that topic (which should be the primary source even without search engine help) and it does naturally have an example that transports a value through the connection.
The suggestion was to use moveToThread() of the worker object which does not require subclassing QThread.
Cheers,
_
Bookmarks