view doc/gtklog-signals.dox @ 28882:36daf22b09f6

I think this is only the place this could leak... ==14064== 36 bytes in 2 blocks are definitely lost in loss record 13,092 of 20,211 ==14064== at 0x4024C1C: malloc (vg_replace_malloc.c:195) ==14064== by 0x4A73B0F: __vasprintf_chk (vasprintf_chk.c:82) ==14064== by 0x485197E: g_vasprintf (in /lib/libglib-2.0.so.0.2200.3) ==14064== by 0x483D485: g_strdup_vprintf (in /lib/libglib-2.0.so.0.2200.3) ==14064== by 0x483D4A7: g_strdup_printf (in /lib/libglib-2.0.so.0.2200.3) ==14064== by 0x492FC6D: purple_mkstemp (util.c:2916) ==14064== by 0x80FEDD5: pidgin_convert_buddy_icon (gtkutils.c:2690)

/** @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