Emmanuele Bassi 6b096e5c5b Make tooltip properties idiomatic ... The tooltip handling in GtkWidget is "special": - the string is stored inside the qdata instead of the private instance data - the accessors call g_object_set() and g_object_get(), and the logic is all inside the property implementation, instead of being the other way around - the getters return a copy of the string - the setters don't really notify all the involved properties The GtkWidgetAccessible uses the (escaped) tooltip text as a source for the accessible object description, which means it has to store the tooltip inside the object qdata, and update its copy at construction and property notification time. We can simplify this whole circus by making the tooltip properties (text and markup) more idiomatic: - notify all side-effect properties - return a constant string from the getter - if tooltip-text is set: - store the text as is - escape the markup and store it separately for the markup getter - if tooltip-markup is set: - store the markup as is - parse the markup and store it separately for the text getter The part of the testtooltips interactive test that checks that the getters are doing the right thing is now part of the gtk testsuite, so we ensure we don't regress in behaviour.		2020-06-05 20:32:26 +01:00
..
a11y
css
gdk
gsk	compare-render: Fix some memory leaks	2020-05-24 17:14:18 +02:00
gtk	Make tooltip properties idiomatic	2020-06-05 20:32:26 +01:00
performance
reftests	reftest: Clean up reftest_inhibit_snapshot()	2020-06-04 15:45:29 +02:00
tools
meson.build