Derek Foreman 7a978fe58c evas_engines: Send both surface and buffer damage to outbuf_flush callback ... Some engines should using sending surface damage, until now we'd only ever provided them with buffer damage. The difference is that surface damage is the damage to the surface the compositor is displaying, and the buffer damage is the damage to the buffer the client has rendered. These are different when the client is using multiple buffers of different ages to render into. Anything that calls eglSwapBuffersWithDamage, wl_surface_damage() or wl_surface_damage_buffer() should be using surface damage, and not buffer damage. This patch is intended to make no functional change - any flush cb that used buffer damage before still should. Actual fixes to follow. Apologies if I broke any engines - it's a bit of a copy and wasteland out here.		2016-10-19 16:29:05 -05:00
..
Evas_Engine_Buffer.h	evas buffer engine: use Eina_Bool for one-bit bitfield	2015-11-13 13:31:34 +01:00
evas_engine.c	evas_engines: Add a redraws_clear callback	2016-09-08 13:55:24 -05:00
evas_engine.h	evas_engines: Send both surface and buffer damage to outbuf_flush callback	2016-10-19 16:29:05 -05:00
evas_outbuf.c	evas_engines: Send both surface and buffer damage to outbuf_flush callback	2016-10-19 16:29:05 -05:00