Jonas Dreßler 9b50215008 clutter/actor: Handle getting (un-)mapped during painting differently ... We currently support only one case where an actor can get mapped or unmapped during painting, that is using _clutter_actor_enable_paint_unmapped() (although we could arguably do a better job explicitely forbidding it in other cases). This function is called when painting ClutterClone or MetaWindowActors during screensharing. It temporarily (fake) realizes and maps the actor and all its children so it can get painted. Now a problem will appear when we'll start coupling layout and the mapped state of actors more closely with the next commit: Since enable_paint_unmapped() is meant to be enabled and disabled during every clone paint, we also notify the "mapped" property twice on every clone paint. That means with the next commit we would queue a relayout for the source actor on every clone paint. To avoid this unnecessary work, check whether we're being painted while unmapped using the new unmapped_paint_branch_counter. Then avoid queuing relayouts or invalidating paint volumes in that case. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1366		2020-10-20 15:27:43 +00:00
..
clutter	clutter/actor: Handle getting (un-)mapped during painting differently	2020-10-20 15:27:43 +00:00
.gitignore	clutter: Remove clutter specific version	2018-11-06 17:17:36 +01:00
meson.build	clutter: Include semi private cogl API	2020-07-02 19:36:50 +02:00