view doc/ui-ops.dox @ 23399:e1bddd9c5c88

jabber_google_roster_add_deny() and jabber_google_roster_rem_deny() previously recreated the iq, query, and item after inserting group information, nullifying the usefulness of having done so. I don't know of a specific problem which this fixes, as I just noticed it while investigating the "jabber:iq:roster" infinite loop discussed on pidgin-devl and in #5484
author Evan Schoenberg <evan.s@dreskin.net>
date Tue, 01 Jul 2008 04:26:19 +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