view doc/ui-ops.dox @ 24963:36897ddd3e08

This should prevent the crash in #8109 by stopping an invalid message from getting in the queue. There is still a problem farther up from here in that an invalid message shouldn't get this far - hopefully this will help track it down by providing a message at the time the issue happens instead of crashing later. Fixes #8109.
author Daniel Atallah <daniel.atallah@gmail.com>
date Thu, 15 Jan 2009 03:54:58 +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