Mercurial > pidgin
view doc/imgstore-signals.dox @ 23662:7b2fdeb078cd
take an extra reference to PurpleXfer so we can check whether the whole
thing went away. I haven't tested this because it's late, but it shouldn't
break things or at least shouldn't make things worse.
It would be great if someone can test this and let me know.
References #6246
author | Ka-Hing Cheung <khc@hxbc.us> |
---|---|
date | Thu, 07 Aug 2008 07:07:32 +0000 |
parents | e0613cf8c493 |
children |
line wrap: on
line source
/** @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