Hello,

I just started looking Evas and Ecore Evas rendering code, and noticed
that the "avoid_damage" option has several implications. From what I
understood, the 3 options are:

 1) ECORE_EVAS_AVOID_DAMAGE_NONE - every expose event triggers a new
damage and consequently render of the affected area. The rendering of
things happens directly on the window;
 2) ECORE_EVAS_AVOID_DAMAGE_EXPOSE - there's a pixmap where everything
is rendered into, and then copied to the window. On expose events,
there's no need to render things again, just to copy the exposed
region to the window;
 3) ECORE_EVAS_AVOID_DAMAGE_BUILT_IN - there's the same pixmap as the
previous one, but it is set as a "background pixmap" of the window.
The rendered things should appear directly on the window, with no need
to copy anything, but would stay stored on the pixmap, so there's no
need to render things again on expose events.

Are the above statements correct? If so, then what's the usefulness of
ECORE_EVAS_AVOID_DAMAGE_EXPOSE, since it seems to me that
ECORE_EVAS_AVOID_DAMAGE_BUILT_IN covers its use case and is faster.

And what I could think of differences between 1) and 3) is that the
later would need to render things using pixman, since it's rendering
in a pixel buffer, while the former could use accelerated xlib calls,
though it has to render things again in the case of expose events. Is
this correct too?

I intend to write a documentation to the damage_set API to better
reflect these options.

Regards,
-- 
Rafael Antognolli
ProFUSION embedded systems
http://profusion.mobi

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to