Hi,
I was looking for a way to improve the situation of Edje's
edje_part_recalc() calling methods to re-apply object properties, even
if they're already the same. For example, if Edje recalc is triggered
(happens every time a singla property changes), it will
move/resize/show/color/... that object.
Looking at evas_object_{move,resize,show,hide,color_set,clip_set}() I
see that it already check, thus it would be "cheaper" to just call
these methods and let them check for the operation, this would save 2
calls to another library (evas_object_*_get() and then _set()).
Evas basic objects (!smart) are handled fine and if these properties
are like the old one, they're just ignored. However smart objects are
handled differently, before informing the call (calling back connected
functions).
So my question is: the calling order is really meant to be like that
or is it just lazy programming?
Actually there are 2 CPP macros "FORWARD_NOOP_RESIZES_TO_SMART_OBJS"
and "FORWARD_NOOP_MOVES_TO_SMART_OBJS" currently defined, do we really
need them? Why don't have similars for hide/show/color/clip...?
As for it breaks current apps to change it off: yes, it does.
Configuration dialog, for instance, don't show it's icons. Not sure if
this is Evas or Edje issue.
--
Gustavo Sverzut Barbieri
--------------------------------------
Jabber: [EMAIL PROTECTED]
MSN: [EMAIL PROTECTED]
ICQ#: 17249123
Skype: gsbarbieri
Mobile: +55 (81) 9927 0010
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
