view doc/gtkconv-signals.dox @ 9191:06b28fb24300

[gaim-migrate @ 9986] " This patch was inspired by Robert Story's previous timestamp patch (#944943). That was rejected because of a timing inconsistency issue mentioned by Faceprint. This patch disables timestamps in a given conversation when no messages have been displayed since the last timestamp. When a new message is about to be displayed in a disabled timestamp conversation, a timestamp is inserted first to maintain timing consistency. Then the timestamp display is reenabled and the IM message is printed. This patch also handles a bug in the original timestamp plugin. Previously, when the timestamp interval was modified in the preferences, no current open conversations are affected. I have modified it so that all open conversations use the new interval. I would have sent this as a separate patch, but this is my first patch and didn't want to mess it up :)." --Eddie Sohn i liked the original patch and was somewhat disappointed that it didn't get fixed to address Nathan's concern, so i'm happy to merge this one in. committer: Tailor Script <[e-mail]>

/** @page gtkconv-signals GtkConv Signals

 @signals
  @signal conversation-drag-ended
 @endsignals

 <hr>

 @signaldef conversation-drag-ended
  @signalproto
void (*conversation-drag-ended)(GaimConvWindow *source, GaimConvWindow *destination);
  @endsignalproto
  @signaldesc
   Emitted when a conversation drag and drop has finished.
  @param source The conversation that has been moved.
  @param destination Where the conversation is now.
 @endsignaldef
*/