Daniel van Vugt 96a185d8bc clutter/stage-cogl: Colour fb_clip_region in CLUTTER_DEBUG_PAINT_DAMAGE_REGION ... Previously when CLUTTER_DEBUG_PAINT_DAMAGE_REGION was set, that would lead to has_buffer_age==FALSE, which would lead to use_clipped_redraw==FALSE which would mean swap_region was always empty. And so the blue region of CLUTTER_DEBUG_PAINT_DAMAGE_REGION was always empty, *and* fb_clip_region was always the full view rectangle which is not useful for debugging. Now when CLUTTER_DEBUG_PAINT_DAMAGE_REGION is set, we don't let that affect use_clipped_redraw, which means fb_clip_region is calculated realistically. But that's not enough. Calculating fb_clip_region properly with CLUTTER_DEBUG_PAINT_DAMAGE_REGION would still lead to colouring artefacts left on screen from previous frames that don't apply to the current frame. So to fix that we also paint_stage for the whole screen every time when using CLUTTER_DEBUG_PAINT_DAMAGE_REGION. So now you will only ever see red and blue shading that's applicable to the current frame, and no artefacts from the previous frames. Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1535 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1571>		2020-11-20 17:14:26 +00:00
..
clutter	clutter/stage-cogl: Colour fb_clip_region in CLUTTER_DEBUG_PAINT_DAMAGE_REGION	2020-11-20 17:14:26 +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