view doc/ui-ops.dox @ 26633:5d1140b0b10a

Don't leak the struct sockaddr* from purple_dnsquery_a. At least one of these gives me: ==00:00:06:28.468 13659== 32 bytes in 2 blocks are definitely lost in loss record 1,020 of 3,383 ==00:00:06:28.468 13659== at 0x04c278ae: malloc (vg_replace_malloc.c:207) ==00:00:06:28.468 13659== by 0x09b29a12: g_malloc (gmem.c:131) ==00:00:06:28.468 13659== by 0x07d2fd8c: host_resolved (dnsquery.c:578)
author Paul Aurich <paul@darkrain42.org>
date Sun, 12 Apr 2009 22:23:34 +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