view doc/ui-ops.dox @ 28672:7e2e95508a3a

Do not create a conversation yet. A plugin can stop a conversation from being created by intercepting the receiving-*-msg signals. But this code would always open a conversation if a '/buzz' is received as the first message. So we end up with an empty conversation window that we didn't create, and it's confusing as poop! Interestingly, I noticed this because the clang-analyzer cried about it. So yay clang-analyzer!
author Sadrul Habib Chowdhury <imadil@gmail.com>
date Mon, 28 Sep 2009 17:39:33 +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