view doc/ui-ops.dox @ 31631:feff62713d9c

conversation: Move the "not typing" logic for receipt of a message to purple_conv_im_write. This causes issues when a UI implements the write_im UI op and doesn't call purple_conversation_write (which Spectrum doesn't do), and ends up with a buddy appearing to be stuck in the typing state. Patch from Jan "HanzZ" Kaluza committer: Paul Aurich <paul@darkrain42.org>
author hanzz.k@gmail.com
date Sat, 05 Feb 2011 22:38:55 +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