Alexander Orzechowski 7ba7f774ca wlr_compositor: Introduce wlr_surface_consume ... If the compositor is running without a renderer, that means that the compositor must be driven by something external that may or may not be there. So we have two scenarios: 1. This compositor is currently being watched and driven by some external source that is consuming buffers. This is okay, because during the commit handler `surface->current.buffer` and `surface->buffer_damage` will be usable and things will be handled like normal. 2. Things break however if the compositor is not currently driven. This however is commonly temporary. Something may not be interested right now, but later it can be. In this case we have to accumulate state until this external consumer is ready. Here, we have to accumulate the `buffer_damage` and keep the buffer locked until the consumer is ready. `wlr_surface_consume` needs to be called when the state of this surface was consumed so that it is safe to release these resources.		2024-09-14 17:43:56 -04:00
..
backend	backend/drm: add explicit sync support to multi-GPU blits	2024-08-26 18:09:27 +02:00
interfaces	types/wlr_input_device: move init and finish function to private API	2022-03-07 16:37:41 +00:00
render	render/color: Invert ownership model of color_transform types.	2024-08-24 14:33:22 -04:00
types	cursor: add support for linux-drm-syncobj-v1	2024-08-06 17:37:06 +00:00
util	xdg-toplevel: check that title provided actually is UTF-8	2023-11-22 22:03:00 +03:00
wlr	wlr_compositor: Introduce wlr_surface_consume	2024-09-14 17:43:56 -04:00
xcursor	Add some missing includes/declarations	2023-06-05 21:06:19 +00:00
xwayland	xwayland/xwm: listen shell destroy signal	2024-08-13 11:33:04 +08:00
meson.build	render/color: add fallback stub when LCMS2 is disabled	2024-06-04 17:45:51 +00:00