Cedric wrote:
> If understood the code correctly, when I change a property that
> could affect the layout of the edje, _edje_calc is called directly
> instead of being defered until render like all native evas_object
> behaviour. That's because smart object don't have a render_pre
> function. It also need to recalculate all edje part, because their
> is actually no way to know what are the part that would be affected
> by the change of another part.
Exactly. It's a real source of inefficiency for most any
smart-class derived object that needs heavy calculations and/or uses
custom rendering.
One'd need to add render_pre/post functions to smart classes
(very easy to do), and have these called, if there, from the smart
object's internal render_pre/post obj functions.
There are a couple of other smart class functions that would
also be useful with smart objects, in particular min/max_size_get
functions, and add similar functions to the evas api so that one can
query an evas object's min/max size.
jose.
_____________________________________________________________
Click for free info on online masters degrees and make up to $150K/ year
http://thirdpartyoffers.juno.com/TGL2121/fc/Ioyw6i3nNjcaHVAzCuFMV4rAE8pAP1h4qQQrzhXWs1Z3o2Hr0gub1m/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
