On Wed, Dec 19, 2012 at 1:27 AM, Enlightenment SVN <no-re...@enlightenment.org> wrote: > Log: > ecore-evas: Async render > > > Author: acidx > Date: 2012-12-18 08:27:26 -0800 (Tue, 18 Dec 2012) > New Revision: 81283 > Trac: http://trac.enlightenment.org/e/changeset/81283
I am just starting to look at this evas async rendering and I am not a big fan of the prototype of evas_render_async. Why do we need to duplicate the evas event infra and specify the Evas_Event_Cb per call to evas_render_async ? It seems to me EVAS_CALLBACK_RENDER_POST should do the job just fine. At the same time I don't like the idea of directly giving an Eina_List for update. It should be put in a proper public structure like all others events structure and the list will just be a member of it. Of course that structure should also be send with evas_event_callback_call instead of the current NULL. -- Cedric BAIL ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
