Cedric BAIL a7f2974e13 * evas: break engine API !!! ... Improvements: Now evas rendering loop is the one responsible to initialize the surface to 0 correctly (taking into account surface alpha and object opacity). This will reduce the number of memset we do. Note: Current software_x11 (xlib and xcb) are buggy. They are copying too much data when the surface use a mask. That's why two memset are left in their code. They could be removed, but we should fix the surface we copy on change (look at mxob user and evas_software_xlib_x_output_buffer_paste). SVN revision: 41206		2009-06-26 13:26:52 +00:00
legacy	* evas: break engine API !!!	2009-06-26 13:26:52 +00:00