Mercurial > pidgin
view doc/imgstore-signals.dox @ 24386:6e4979001d6d
The "processing" flag basically says "this connection is busy, don't
destroy it yet, wait until it's done processing."
I don't think there's any reason for us to set processing to TRUE just
because we're connecting. I think this is a holdover from before our
purple_proxy_connect() could be canceled. But now that it's cancelable,
if we want to kill the connection we can cleanly cancel the connect
without worrying about the callback being triggered.
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Wed, 12 Nov 2008 09:10:29 +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