Mercurial > pidgin.yaz
view doc/imgstore-signals.dox @ 20536:d52d299cfde3
seems to fix duplicate oim messages for real. The problem was that MSN tells
us about the OIMs twice, one during sign on and one after sign on
the fix is to keep track of OIMs until we delete them, and not request for
OIMs that are already requested
Fixes #3345
author | Ka-Hing Cheung <khc@hxbc.us> |
---|---|
date | Wed, 03 Oct 2007 04:18:36 +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