view doc/gtklog-signals.dox @ 28880:5063f721de6d

We really shouldn't be doing a whole lot in our signal handler. The signal handler can get called in the middle of a malloc, for example, and if the signal handler tries to allocate memory then the program can deadlock. This change works around that problem by having the signal handler write to a pipe. Our main program watches the pipe for incoming data and performs the appropriate action. This patch is from Shaun Lindsay at Meebo. Fixes #10324

/** @page gtklog-signals GtkLog Signals

 @signals
  @signal log-displaying
 @endsignals

 @see gtklog.h

 <hr>

 @signaldef log-displaying
  @signalproto
void (*log_displaying)(PidginLogViewer *viewer, PurpleLog *log);
  @endsignalproto
  @signaldesc
   Emitted when a log is being displayed.
  @param viewer The log viewer
  @param log The log being displayed
 @endsignaldef

*/
// vim: syntax=c.doxygen tw=75 et