7 Commits

Author	SHA1	Message	Date
Matthias Clasen	7cb36aba40	Load theme settings from the right location ... When loading a per-theme settings.ini file, look for it in the same directory where we found the gtk.css file for the theme. Previously, we were always looking in $prefix/share/themes/THEME/gtk-3.0/, even if the css was loaded from somewhere else. https://bugzilla.gnome.org/show_bug.cgi?id=641354	2016-03-21 22:19:19 -04:00
Matthias Clasen	2952739593	GtkCssProvider: Allow to enable debug at runtime ... Add a private function that lets us decide at runtime whether to keep css section information around - this will be useful in the GtkInspector.	2014-07-06 22:37:57 -04:00
Benjamin Otte	738b453c66	cssprovider: Export gtk_css_provider_load_named) function ... ... and document it. For now, the function is only exported internally.	2012-10-31 11:09:09 +01:00
Matthias Clasen	ab3d6a0b0a	Revert "Bind the themes to the livecycle of the screen" ... This reverts commit 1f5dea9eba, since it was causeing noticable behaviour changes. Previously, GTK_DATA_PREFIX=/ ./gtk3-demo would start gtk3-demo with the Raleigh theme. With that change, it was starting with no theme at all (i.e. all black).	2012-09-17 22:31:25 -04:00
William Jon McCann	1f5dea9eba	Bind the themes to the lifecycle of the screen ... https://bugzilla.gnome.org/show_bug.cgi?id=683896	2012-09-16 20:20:44 -04:00
Javier Jardón	9d0febc9a6	Change FSF Address	2012-02-27 17:06:11 +00:00
Matthias Clasen	ea24fa62c8	Privately export css_provider_get_theme_dir	2011-01-27 00:32:07 -05:00