From 681a72ea9923a3b37d8258b2b25e8f734d92bf21 Mon Sep 17 00:00:00 2001 From: Ryan Lortie Date: Sun, 12 Sep 2010 13:35:30 -0400 Subject: [PATCH] GSettings: no writability->value change assumption GSettings internally assumed that a change in key writability implied a change in value. That may be true for some backends. Let those backends deal with the situation for themselves. --- gio/gsettings.c | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/gio/gsettings.c b/gio/gsettings.c index b8f0d30..eb4370c 100644 --- a/gio/gsettings.c +++ b/gio/gsettings.c @@ -249,14 +249,8 @@ g_settings_real_writable_change_event (GSettings *settings, keys = g_settings_schema_list (settings->priv->schema, &n_keys); for (i = 0; i < n_keys; i++) - { - const gchar *string = g_quark_to_string (keys[i]); - - g_signal_emit (settings, g_settings_signals[SIGNAL_WRITABLE_CHANGED], - keys[i], string); - g_signal_emit (settings, g_settings_signals[SIGNAL_CHANGED], - keys[i], string); - } + g_signal_emit (settings, g_settings_signals[SIGNAL_WRITABLE_CHANGED], + keys[i], g_quark_to_string (keys[i])); return FALSE; } -- 2.7.4