Mercurial > pidgin
view doc/imgstore-signals.dox @ 22242:d5b65bead569
Yahoo! has no permit list, so get rid of the add_permit and rem_permit prpl
callbacks. Right now they're basically a no-op. More specifically,
purple_privacy_permit_add calls serv_add_permit which calls
yahoo_add_permit which calls purple_privacy_permit_add (again) which
exits because the buddy is already in the permit list.
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Fri, 01 Feb 2008 02:05: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