view doc/imgstore-signals.dox @ 22245:31863f2d7c3c

Our Yahoo! protocol has this crappy implementation where it tries to do something clever with the permit/deny setting. Here's how it works: * Yahoo! has only a "deny" list * libpurple keeps a copy of this "deny" list * If you change your permdeny setting to "allow all" or "permit only these users" then the Yahoo! PRPL unblocks everyone on your deny list * If you change your permdeny setting to "allow people in my buddylist" or "block this people below" then the Yahoo! PRPL re-blocks the people in your deny list. This commit changes that behavior slightly. If you set your permdeny setting to "permit only these users" or "block everyone" then the Yahoo! PRPL will now re-block the people in your deny list.

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