GNOME Bugzilla – Bug 632538
Move setting property registration in gtksettings.c
Last modified: 2010-10-20 09:35:55 UTC
Registering settings properties in different classes means that there is an undocumented prerequisite to instantiate that class in order to set a GtkSettings property - or get a warning from GObject that the property does not exist. The attached patch moves back all GtkSettings properties scattered throughout gtk+ -- except for the one in GtkColorSel, because the default value is used internally as a fallback, and I'd like some feedback on how to handle it properly.
Created attachment 172690 [details] [review] settings: Move setting property registration in gtksettings.c Some GtkSettings property are registered by other classes. This leads to the "interesting" issue that setting GtkSettings:gtk-button-images requires that the GtkButton class is referenced first - or that a GtkButton is created.
There are a few more settings in gtkimcontextxim.c: "gtk-im-preedit-style", "gtk-im-status-style" (see bug 585166).
Created attachment 172748 [details] [review] settings: Move setting property registration in gtksettings.c Some GtkSettings property are registered by other classes. This leads to the "interesting" issue that setting GtkSettings:gtk-button-images requires that the GtkButton class is referenced first - or that a GtkButton is created.
*** Bug 585166 has been marked as a duplicate of this bug. ***
Attachment 172748 [details] pushed as 9f9edb6 - settings: Move setting property registration in gtksettings.c