view doc/imgstore-signals.dox @ 24134:aa8ddc4e12af

GtkBlist: don't set the Urgent hint whenever a connection error occurs or is updated In principle, setting Urgent is a good idea, because the user can tell that an error has occurred. However, it winds up being repeatedly re-set every time an account tries and fails to reconnect, which is incredibly annoying. I think the right solution is to keep a set of accounts we've set urgent for, removing them from the set when they successfully connect. But not setting it at all is better than the current state.
author Will Thompson <will.thompson@collabora.co.uk>
date Sun, 28 Sep 2008 17:19:38 +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