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.

diff --git a/gio/gsettings.c b/gio/gsettings.c
index b8f0d30..eb4370c 100644 (file)
--- 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++)
     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;
 }
 
   return FALSE;
 }