> > struct _Edje
> > {
> > + Evas_Object *clipper; /* a big rect to clip this Edje to */
> > + Evas *evas; /* the Evas this Edje belongs to */
>
> This is a bit dangerous and not recommended as you'd have to keep in
> sync. Technically it's fine as they have the same layout, but I'd have
> as first field:
You are entirely correct. The reason I did that way (at first) was to
minimise the delta for the change and testing (and I was just happy[1] it
worked first go).
I'll punt it over.
Regards,
nash
[1] For values of happy best described as 'surprised and confused'.
------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
