view src/dbus-define-api.h @ 11261:b53606580f68

[gaim-migrate @ 13439] Patch #1226486 from Levi Bard Fixes bug #1224178 If you change the topic in a chat room and that topic change is rejected, the topic field is wrong -- it shows the new topic even thought it didn't get set. This patch resets the GUI's topic immediately when you hit enter. Then, if the topic change is successful, the server will echo the topic change back to us and we'll update the GUI to the new topic. The only question is, does the server always echo the topic back to us? From the core's point of view, I'm ready to assume yes. It's the case for both IRC and Jabber*. If someone could test changing a topic in SILC or Zephyr, that'd be great. If servers using those protocols do not echo the topic back, the prpl will have to fake it as appropriate. * I didn't actually test on Jabber, but Nathan said the server will echo the topic change back. If it's broken, let me know. committer: Tailor Script <[e-mail]>

#error "This is file is not a valid C code"

/* This file contains some of the macros from other header files as
   function declarations.  This does not make sense in C, but it
   provides type information for the dbus-analyze-functions.py
   program, which makes these macros callable by DBUS.  */

/* blist.h */
gboolean GAIM_BLIST_NODE_IS_CHAT(GaimBlistNode *node);
gboolean GAIM_BLIST_NODE_IS_BUDDY(GaimBlistNode *node);   
gboolean GAIM_BLIST_NODE_IS_CONTACT(GaimBlistNode *node);
gboolean GAIM_BLIST_NODE_IS_GROUP(GaimBlistNode *node);
gboolean GAIM_BUDDY_IS_ONLINE(GaimBuddy *buddy); 
gboolean GAIM_BLIST_NODE_HAS_FLAG(GaimBlistNode *node, int flags);
gboolean GAIM_BLIST_NODE_SHOULD_SAVE(GaimBlistNode *node);

/* connection.h */
gboolean GAIM_CONNECTION_IS_CONNECTED(GaimConnection *connection);
gboolean GAIM_CONNECTION_IS_VALID(GaimConnection *connection);

/* conversation.h */
GaimConvIm *GAIM_CONV_IM(const GaimConversation *conversation);
GaimConvIm *GAIM_CONV_CHAT(const GaimConversation *conversation);