Mercurial > pidgin.yaz
view doc/imgstore-signals.dox @ 18155:094698b04630
Based on my calculations, this comment made no sense. It is not necessary to
add a pref before deleting it, and emptying the function doesn't break the API.
I am also changing an instance of purple_prefs_rename() into _remove() because
it would rename a preference to the one that is being removed anyway.
author | Kevin Stange <kevin@simguy.net> |
---|---|
date | Sun, 17 Jun 2007 07:46:04 +0000 |
parents | 61ddeb85ab86 |
children | e0613cf8c493 |
line wrap: on
line source
/** @page imgstore-signals Image Store Signals @signals @signal image-deleting @endsignals <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 tw=75 et