summaryrefslogtreecommitdiff
path: root/gtk/gtkcssstylechange.c
Commit message (Collapse)AuthorAgeFilesLines
* css: Fix an oversight in style change computationMatthias Clasen2020-02-021-8/+31
| | | | | Take the 'color == NULL means currentColor' trick into account when computing the changes between two styles.
* Compute style change based on values structsMatthias Clasen2020-01-291-42/+64
| | | | | | We can save some time here by comparing struct by struct and avoiding individual values comparisons as much as possible.
* GtkCssStyleChange: Only print values that really changedTimm Bäder2017-10-121-0/+4
|
* cssstylechange: Fix change printingTimm Bäder2017-07-221-3/+1
| | | | Only print the old value once, above the new one.
* cssstylechange: Add helper function to print changeTimm Bäder2016-02-071-0/+44
| | | | | So I don't have to print both styles to the console, paste them both into a file and then run diff on the 2 files anymore.
* stylechange: Do the right thing when old and new style are equalBenjamin Otte2016-01-161-0/+4
| | | | | We don't need to compare all their CSS values to figure out that nothing changed. We know that.
* widget: Pass a GtkCssStyleChange instead of a bitmaskBenjamin Otte2015-12-131-3/+14
|
* cssnode: Change style-changed signalBenjamin Otte2015-12-121-0/+97
Instead of having old and new style, now have a GtkCssStyleChange opaque object that will compute the changes you are interested in for you. This simplifies change signal handlers quite a bit and avoids lots of repeated computation in every signal handler.