Mercurial > pidgin

view doc/ui-ops.dox @ 28749:819f464e581c

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
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 e3bf822c19c8
children
line wrap: on
line source

/** @page ui-ops UiOps structures

  When implementing a UI for libpurple, you need to fill in various UiOps
  structures:

   - #PurpleAccountUiOps
   - #PurpleBlistUiOps
   - #PurpleConnectionUiOps
   - #PurpleConversationUiOps
   - #PurpleCoreUiOps
   - #PurpleDebugUiOps
   - #PurpleDnsQueryUiOps
   - #PurpleEventLoopUiOps (without this, nothing will work and you will cry)
   - #PurpleIdleUiOps
   - #PurpleNotifyUiOps
   - #PurplePrivacyUiOps
   - #PurpleRequestUiOps
   - #PurpleRoomlistUiOps
   - #PurpleSoundUiOps
   - #PurpleWhiteboardUiOps
   - #PurpleXferUiOps

 */
// vim: ft=c.doxygen