view doc/gtkconv-signals.dox @ 9798:255596f41014

[gaim-migrate @ 10666] This is patch number 1002252 by Joe Shaw. He writes: If you start a file transfer with a yahoo user and then unplug the network, wait a couple minutes, and plug it back in, a minute or so later the gaim UI will completely freeze, eventually consume all your memory and crash. This is because ft.c:transfer_cb() does not correctly handle the case in which both READ and WRITE conditions are coming in, and because the yahoo_xfer_read() and yahoo_xfer_write() functions are incorrectly returning 0 on errors instead of -1. Since transfer_cb() is getting both conditions, it only checks READ first and gets back 0 bytes (because the connection has been hung up). 0 is not explicitly handled, so nothing is done and we get ourselves into an infinite loop. 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
*/