summaryrefslogtreecommitdiff
path: root/gtk/gtkcssstylefuncsprivate.h
Commit message (Collapse)AuthorAgeFilesLines
* cssvalue: Remove GtkCssDependenciesBenjamin Otte2015-03-181-2/+1
| | | | They are not used anymore.
* cssstyle: Rename GtkCssComputedValues => GtkCssStyleBenjamin Otte2015-01-071-2/+2
| | | | | This is literally just renaming of the object (and the associated source files). No other changes are in there.
* cssstylefuncs: Rename functionsBenjamin Otte2015-01-071-3/+3
| | | | | This is in preaparation for the big GtkCssComputedValues => GtkCssStyle rename
* css: Huge refactoring to avoid computing wrong valuesBenjamin Otte2012-09-281-8/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Here's the shortest description of the bug I can come up with: When computing values, we have 3 kinds of dependencies: (1) other properties ("currentColor" or em values) (2) inherited properties ("inherit") (3) generic things from the theme (@keyframes or @define-color) Previously, we passed the GtkStyleContext as an argument, because it provided these 3 things using: (1) _gtk_style_context_peek_property() (2) _gtk_style_context_peek_property(gtk_style_context_get_parent()) (3) context->priv->cascade However, this makes it impossible to lookup values other than the ones accessible via _gtk_style_context_peek_property(). And this is exactly what we are doing in gtk_style_context_update_cache(). So when the cache updates encountered case (1), they were looking up the values from the wrong style data. So this large patch essentially does nothing but replace the context argument in all compute functions with new arguments for the 3 cases above: (1) values (2) parent_values (3) provider We apparently have a lot of computing code.
* cssvalue: Handle dependencies for typed valuesBenjamin Otte2012-08-281-1/+2
|
* cssstylefuncs: Remove base argumentBenjamin Otte2012-05-111-2/+1
| | | | The GtkCssParser keeps track of the base file now.
* css: Use GtkCssValues instead of GValue in the css machineryAlexander Larsson2012-03-081-3/+4
| | | | | | Also, in places where we're computing a new CssValue based on an old one, make sure that if nothing changes we're returning a reference to the old one, rather than creating a new identical instance.
* Change FSF AddressJavier Jardón2012-02-271-3/+1
|
* css: Redo value resolvingBenjamin Otte2012-01-091-0/+4
| | | | | | | | | | | | Instead of on-demand resolvage, we now resolve during lookup. The step is done via _gtk_css_style_property_compute_value() which currently calls into _gtk_css_style_compute_value() That function has all the old resolving machinery. The only part missing for now is the handling of win32 code. It will be added back later.
* css: Split generic parse/print functions outBenjamin Otte2012-01-091-0/+35
It seems to be some sort of sport for me to split them out and merge them back in...
View Lorry Controller Status