Jonas Ådahl b73bbecaad clutter/feature: Remove static vs multiple stage feature ... This feature was configured depending on whether the Cogl backend reported COGL_WINSYS_FEATURE_MULTIPLE_ONSCREEN or not. All cogl backends do report this, so any code handled the 'static' case were never used. While we only ever use one stage, it's arguable more correct to consilidate on the single stage case, but multiple stages is something that might be desirable for e.g. a remote lock screen, so lets keep this logic intact. This has the side effect of completely removing backend features, as this was the only left-over feature detection that they handled. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2002>		2021-10-18 14:36:15 +00:00
..
cally-atkcomponent-example.c	tests/clutter: Always use stage from backend	2020-08-13 17:51:56 +02:00
cally-atkeditabletext-example.c	tests/clutter: Always use stage from backend	2020-08-13 17:51:56 +02:00
cally-atkevents-example.c	clutter/feature: Remove static vs multiple stage feature	2021-10-18 14:36:15 +00:00
cally-atktext-example.c	tests/clutter: Always use stage from backend	2020-08-13 17:51:56 +02:00
cally-clone-example.c	tests/clutter: Always use stage from backend	2020-08-13 17:51:56 +02:00
cally-examples-util.c	tests/clutter: Always use stage from backend	2020-08-13 17:51:56 +02:00
cally-examples-util.h	tests/clutter: Always use stage from backend	2020-08-13 17:51:56 +02:00
meson.build	tests: Make common test code a shared library	2021-07-15 13:40:34 +02:00