view doc/ui-ops.dox @ 26806:e07c066b3172

don't uninit accounts until savedstatus and status are uninited, this was never a problem until aff70668336849d4b1513fd8577f4d2a276d2520 which cleaned up accounts (which is itself a good thing) but savedstatus was using the uninitialized accounts (which is a bad thing) mtn using people probably want to check their status.xml for corrupted entries
author Ka-Hing Cheung <khc@hxbc.us>
date Tue, 28 Apr 2009 19:10:04 +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