>i am still tossing up if the smart move method should be there, or all child >objects should be simply placed rlative to the smart parent's origin and thus >moved automatically, or if i should provide a default move method that does >this for you. right now its save from destruction - but i'm tossing up as to >the future of it. > > I think the more logical solution is to have the children placed relative to the smart parent. It will make smart objects looks more like an independant entity. Then of course, a move method has no reason to exist, and if a developer wants to be notified when the smart objects is moved, he can still connect a callback to the event EVAS_CALLBACK_MOVE of the smart object.
Btw, thanks for the work on smart objects, having their own stack fixes a lot of things :) Regards, :) Simon TRENY <MoOm> ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
