| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
| |
We don't need this anymore, now that we use the ::setting-changed
signal.
|
| | |
|
| |
|
|
|
| |
font options are only ever set by the GtkSettings object and only ever
used inside GTK, so just store them there.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This guarantees we only create 1 extra style cascade in total for hidpi
and not one per style context.
Style cascades are now nested like this:
GtkSettings root cascade (scale == 1)
|
+-- GtkSettings per scale cascade (for any scale, no custom providers)
|
+-- GtkStyleContext custom cascade (for any scale, custom providers)
This requires a bunch of care when changing cascade-related properties
inside GtkStyleContext, so that it ends up with a properly setup
cascade, but I think I got those cases right.
The only thing we don't do yet is reverting to a GtkSettings cascade
when the last custom provider is removed from a custom cascade.
|
| |
|
|
|
|
|
|
| |
Settings have a little more metadata than plain properties. They
can come from different sources. Make this information available
so we can show it in the inspector.
https://bugzilla.gnome.org/show_bug.cgi?id=736971
|
| |
|
|
|
| |
We're using this name in two places, so match what we are doing
for the default theme name, and use a macro.
|
| |
|
|
|
| |
This ensures that GTK+ applications have a high-quality theme on
all platforms, and look consistent.
|
| |
|
|
|
|
|
|
| |
This ensures that the initialization for the CSS theme happens when the
style cascade gets queried.
https://bugzilla.redhat.com/show_bug.cgi?id=1064922
https://bugzilla.mozilla.org/show_bug.cgi?id=972382
|
| | |
|
| | |
|
| |
|
