Signals and Slots question

[Thoosle]

wysota, When I look at the docs for QSignalMapper I believe here llies the solution to the problem I was describing. Apparently, when a widget is created I can set a mapping to it from the "emitter" based on the widgets id so that signals from the "emitter" are mapped to the appropriate widget. I will "connect" to all the widgets but only send messages to their intended destination, which is the desired operation. In the QSignalMapper "Detailed Description" it examples using QSignalMapper to setmappings for a group of buttons to signal a slot with eachs buttons text id thus bundling the buttons signals. What I'm wanting to do is like the inverse of that. Do you agree my conclusions in this or have I missed the point? BTW, I'm thinking that the "emitter" and widgets will run in their own threads, hence the desire for signals/slots. Thanks again for your insights....

[wysota]

QSignalMapper does a many-to-one mapping and as you said, you want the opposite. The code I've written in the previous post more or less does exactly that. It just isn't thread safe, so if you wish to use threads for your receivers, you need to modify it. I would even suggest to use custom events instead of signals and slots, this way instead of rcv->receive(...) you'd simply call QCoreApplication::postEvent(rcv, new MessageEvent(...)). Then it's just a matter of reimpementing customEvent() to handle the event and implementing the custom event class (MessageEvent).

[Thoosle]

wysota, this discussion is most helpful and enlightening for me. I'll take a look at your suggestions. Again, thanks very much for your insights....