view src/dbus-define-api.h @ 13131:47ecef83e2e1

[gaim-migrate @ 15493] A lot of our conversation code assumes that conv->account != NULL. This is a completely invalid assumption. If you have a conversation open on an account, and you delete the account, Gaim should leave the conversation window open and set the account to NULL and handle everything appropriately. Currently it does not, and that makes me a little unhappy. To reproduce this: 1. Open a conversation with someone 2. Delete the account that you're sending messages from 3. Watch the assertion failures scroll by in the debug window 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);