> The protocol plugins have no way to directly give an EventTag, so > there is a special signal that the protocol plugin pushes on to the UI > plugins. SIGNAL_EVENTxID contains the Event Tag. In the Qt GUI, > signal_eventTag() gets called when we receive this signal. > Which in turn triggers CMainWindow::slot_eventTag(). From there we add > the event tag to the queue.
I've come across a bit of a problem with the RMS plugin when dealing with SIGNAL_EVENTxID. Say there are 2 clients connected to RMS, and they both send a message to the same contact. RMS will then get SIGNAL_EVENTxID's - how will it know which is for which client? Perhaps when the plugin does ProtoSendMessage() or whatever, it also passes some kind of unique identifier (which it keeps track of - in the case of RMS, which client it belongs to), which is held and passed back in the event with the SIGNAL_EVENTxID, so that the plugin can tell what it's for.. Any other suggestions? Philip ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Licq-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-devel
