Mercurial > pidgin
view doc/cipher-signals.dox @ 28749:819f464e581c
Make sure that libpurple core knows that a buddy is on the allow list just
after accepting their add request. Previously, this was not a problem, and
would go away at next login, but now that the core does its own client-side
blocking, it appears as if newly added buddies can't talk to you.
Fixes #10898.
author | Elliott Sales de Andrade <qulogic@pidgin.im> |
---|---|
date | Wed, 09 Dec 2009 03:02:03 +0000 |
parents | e0613cf8c493 |
children |
line wrap: on
line source
/** @page cipher-signals Cipher Signals @signals @signal cipher-added @signal cipher-removed @endsignals @see cipher.h <hr> @signaldef cipher-added @signalproto void (*cipher_added)(PurpleCipher *cipher); @endsignalproto @signaldesc Emitted when a cipher is added. @param cipher The cipher that was added. @endsignaldef @signaldef cipher-removed @signalproto void (*cipher_removed)(PurpleCipher *cipher); @endsignalproto @signaldesc Emitted when a cipher is removed. @param cipher The cipher that was removed. @endsignaldef */ // vim: syntax=c.doxygen tw=75 et