On Sun, Apr 13, 2008 at 7:42 PM, Peter Wehrfritz <[EMAIL PROTECTED]> wrote:
> Gustavo Sverzut Barbieri schrieb:
>
> > Maybe it will not impact things. The problem with these calls is that
>  > they would collide with Edje internal states, getting these
>  > inconsistent. But since Edje does not handle any layer/stack-related
>  > information in their states, maybe this is no problem, in this case
>  > just add the call to edje C api (edje_object_part_{raise,lower}()) and
>  > expose it from embryo.
>  >
>  I don't think it is a good idea to have those functions in the edje c
>  api. The application should change directly the theme. That's why there
>  isn't a edje_object_part_state_set() function.

While I'm unsure whenever to have or not this function exported, this
is different from what you said: part_state_set() can be done with
signals, while there are no means to reorder the objects from edje,
neither from states or code. Maybe the reason to not have this known
by someone (raster?), maybe it was just left out due out-of-time, in
that case we could add this to Edje states and use signals to trigger
changes.

Lars: what's your motivation to use this? maybe this can give us some light.

-- 
Gustavo Sverzut Barbieri
http://profusion.mobi
Embedded Systems
--------------------------------------
MSN: [EMAIL PROTECTED]
Skype: gsbarbieri
Mobile: +55 (81) 9927 0010

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to