Hi, Gustavo Sverzut Barbieri <barbi...@profusion.mobi> writes:
> That may be another bug, we did not test but the current patch indeed > fixes the problem, discarding the previous surface sooner than later. > > If you want another function, there is no need to mark it as > dirty/changed, just isolate the mapped surface cleanup code into a > function, call it from everywhere (the one that checks if there is a > map and its surface, deleting them) -- no need for a new flag, but I > like your proposed name evas_object_content_change() OK, I fully agree with both of you guys. Looking forward to have that code in evas_render.c. -- Paulo Cavalcanti, Intel Open Source Technology Center I speak only for myself. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel