You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Alexander Orzechowski a32180afa7 wlr_scene: Fix damage tracking with non atomic opaque region configuration ... We need to intersect the opaque region with the node size or else we'll get damage tracking effects with compositors attempting to use wlr_scene_buffer_set_opaque_region() along with resizing the buffer at the same time in a certain order. Consider this: I have a new buffer that I want to commit to my scene buffer that is smaller than the old one. However, I still have the old opaque region that is the size of the old larger buffer, so that means that for the small moment between when we reconfigure the opaque region for the new buffer the opaque region will be oversized. Scene logic will then try to apply occluding optimizations outside of the node boundaries causing damage artifacts.		1 year ago
..
drag_icon.c	drag: use unified map logic	2 years ago
layer_shell_v1.c	layer-shell: use unified map logic	2 years ago
output_layout.c	scene/output_layout: Fix crash in scene_output_layout_output_destroy	3 years ago
subsurface_tree.c	subcompositor: use unified map logic	2 years ago
surface.c	scene: send wl_surface.preferred_buffer_scale	1 year ago
wlr_scene.c	wlr_scene: Fix damage tracking with non atomic opaque region configuration	1 year ago
xdg_shell.c	xdg-shell: use unified map logic	2 years ago