diff options
author | Ankit Vani <a@nevitus.org> | 2014-01-12 16:17:47 +0530 |
---|---|---|
committer | Ankit Vani <a@nevitus.org> | 2014-01-12 16:17:47 +0530 |
commit | 9c4540b6c06294326c99c4146afbeb072478ce2a (patch) | |
tree | 34492d31bcf1b0cbff679c33d6a2e79cd5dc3be4 /libpurple/prefs.c | |
parent | 638cc14f94cde32de4a526b2d446c33e26931944 (diff) | |
parent | d2cbe13b696378ef2abd7b8379b80bf029223ae4 (diff) | |
download | pidgin-9c4540b6c06294326c99c4146afbeb072478ce2a.tar.gz |
Merged default branch
Diffstat (limited to 'libpurple/prefs.c')
-rw-r--r-- | libpurple/prefs.c | 20 |
1 files changed, 5 insertions, 15 deletions
diff --git a/libpurple/prefs.c b/libpurple/prefs.c index 78e6258645..e1063929bf 100644 --- a/libpurple/prefs.c +++ b/libpurple/prefs.c @@ -51,6 +51,11 @@ struct purple_pref { PurplePrefType type; char *name; union { + /* 'generic' is kind of ugly. We use it as an elegant way to refer to + the value of this pref when calling callback functions. We could + use 'boolean' or 'integer' or any other field... but it feels + mildly cleaner to use a gpointer. Maybe it would be best to use a + GValue? */ gpointer generic; gboolean boolean; int integer; @@ -782,21 +787,6 @@ purple_prefs_trigger_callback(const char *name) } void -purple_prefs_set_generic(const char *name, gpointer value) -{ - struct purple_pref *pref = find_pref(name); - - if(!pref) { - purple_debug_error("prefs", - "purple_prefs_set_generic: Unknown pref %s\n", name); - return; - } - - pref->value.generic = value; - do_callbacks(name, pref); -} - -void purple_prefs_set_bool(const char *name, gboolean value) { struct purple_pref *pref = find_pref(name); |