view doc/imgstore-signals.dox @ 23322:0d47aab4ca5c

Patch from Andrew Gaul that fixes a leak: ==13094== 190 (112 direct, 78 indirect) bytes in 6 blocks are definitely lost in loss record 111 of 290 ==13094== at 0x4A05854: calloc (vg_replace_malloc.c:397) ==13094== by 0x331303F849: g_malloc0 (in /lib64/libglib-2.0.so.0.1600.3) ==13094== by 0x47C5BE: text_tag_data_new (gtkimhtml.c:5121) ==13094== by 0x47C9CC: gtk_imhtml_get_markup_range (gtkimhtml.c:5198) ==13094== by 0x46EAEF: gtk_imhtml_clipboard_get (gtkimhtml.c:1007)

/** @page imgstore-signals Image Store Signals

 @signals
  @signal image-deleting
 @endsignals

 @see imgstore.h

 <hr>

 @signaldef image-deleting
  @signalproto
char *(*image_deleting)(const PurpleStoredImage *img);
  @endsignalproto
  @signaldesc
   Emitted when a #PurpleStoredImage is about to be destroyed.  This allows
   for what amounts to weak references.  Code can hold onto a pointer to
   the PurpleStoredImage without actually "holding" a reference.  They can
   then use a signal handler to let them know when their img is about to
   be destroyed.
  @param img The image about to be destroyed.
  @note It's not possible to purple_imgstore_ref() img to save it.
 @endsignaldef

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