comparison libpurple/blist.h @ 32474:53ae12ee0b68

pidgin: Fix so that logging works again This was broken in 941f205e71bee6f0fe79442af21238c088eecbac. The semantics are that the global setting is used if a per-blist-node doesn't exist. This requires we know whether one exists or not (value being non-NULL previously), hence the new API. I was going to add this as _get_type(), but I thought I remembered we were trying to move away from PurpleValue. Anyway, feel free to fix this another way before 3.0.0. Thanks to dvpdiner2 for narrowing down the offending commit.
author Paul Aurich <paul@darkrain42.org>
date Sun, 15 Jan 2012 05:50:58 +0000
parents 98520ee78f12
children
comparison
equal deleted inserted replaced
32473:6ffb26b8a8ce 32474:53ae12ee0b68
1050 * buddy list. 1050 * buddy list.
1051 */ 1051 */
1052 void purple_blist_request_add_group(void); 1052 void purple_blist_request_add_group(void);
1053 1053
1054 /** 1054 /**
1055 * Checks whether a named setting exists for a node in the buddy list
1056 *
1057 * @param node The node to check from which to check settings
1058 * @param key The identifier of the data
1059 *
1060 * @return TRUE if a value exists, or FALSE if there is no setting
1061 */
1062 gboolean purple_blist_node_has_setting(PurpleBlistNode *node, const char *key);
1063
1064 /**
1055 * Associates a boolean with a node in the buddy list 1065 * Associates a boolean with a node in the buddy list
1056 * 1066 *
1057 * @param node The node to associate the data with 1067 * @param node The node to associate the data with
1058 * @param key The identifier for the data 1068 * @param key The identifier for the data
1059 * @param value The value to set 1069 * @param value The value to set