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_Software_Generic.h	evas_engines: Send both surface and buffer damage to outbuf_flush callback	2016-10-19 16:29:05 -05:00
evas_ector_software_buffer.c	evas: Fix async filters following changes in EO	2016-10-06 12:24:59 +09:00
evas_ector_software_buffer.eo	Change the EFL to follow the new Eo rename.	2016-08-11 17:04:43 +01:00
evas_engine.c	evas_engines: Send both surface and buffer damage to outbuf_flush callback	2016-10-19 16:29:05 -05:00
evas_native_common.h	evas/gl_x11 : Add multiple_buffer member in native surface x11 type union.	2016-08-17 17:56:17 +09:00
evas_native_dmabuf.c	software_generic: Add wayland dmabuf native surface support	2016-05-18 11:52:24 -05:00
evas_native_tbm.c	evas: native-tbm: remove unused variable	2016-06-20 16:07:20 +02:00