On Mon, Jan 9, 2012 at 3:46 PM, Bruno Dilly <bdi...@profusion.mobi> wrote: > On Mon, Jan 9, 2012 at 11:26 AM, Cedric BAIL <cedric.b...@free.fr> wrote: >> On Mon, Jan 9, 2012 at 2:06 PM, Bruno Dilly <bdi...@profusion.mobi> wrote: >>> On Sun, Jan 8, 2012 at 2:32 PM, Cedric BAIL <cedric.b...@free.fr> wrote: >>>> On Sun, Jan 8, 2012 at 3:47 PM, ChunEon Park <her...@naver.com> wrote: >>>>> I think both are no problems if it has a documentation. >>>>> But your patch may break applications already released. >>>>> It will be better to apply your patch when major version is changed. >>>> >>>> As I say, current behaviour is undefined. If you go out of an >>>> animation (defined in the edj itself) in any state (hidden, moved, >>>> resized, whatever), it will stay in that state. But this is completly >>>> random and not defined (as in, depend on an external file). Now I do >>>> like the raster proposal with an orphaned flag as it is the only sane >>>> way to detect any leak. Relying on an undefined visual artefact would >>>> not help at all. >>> >>> It isn't documented. But it's defined, IMHO, since you can predict it. >>> As you said, in an animation it will keep the state, if it was >>> visible, it will stay visible. >>> So applications can be considering a unswallowed object will be >>> visible, since it was visible, and now it will be hidden. >> >> No, as it is defined in the theme, it doesn't depend on the >> application. If you change the theme, the animation, anything in the >> .edj, it will change the behaviour in the application itself. It's >> full of race condition. There is no sane way to expect any kind of >> behaviour in the app. It is definitivly an undefined behaviour, as >> their is no way you could know the state of the object without >> requesting it after the unswallow. > > OK, my concept of application is code and theme. > Anyway, a simple case is to add an rectangle to a swallow in a layout. > I've attached a quick example. As you can see, no luck required. After > 3 seconds the rectangle is unswallowed and displayed at 0,0.
Ok, I see the difference. From my point of view, the application should never trust an edj file. So if I can break your "consistent" behaviour by just touching the edc file, then their is a bug in the application from my point of view. In your example. I just need to set visible: 0, or rel1.relative: 0 0; and rel2.relative: 0 0; to break your app. So you are just lucky that no one touched your edc file. >From my point of view, an edj is a black box that can do anything. There is no such thing like when I unswallow all my theme will always resize the object and make them properly visible. That's why I see this as an undefined behaviour. -- Cedric BAIL ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
