On Thu, 27 Oct 2005 17:00:10 +0200 Simon TRENY <[EMAIL PROTECTED]> babbled:
> > >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 :) well it seems after some trials and tribulations - the sub-stack is now working well for everyone. now placing objects RELATIVe to their parent is much mroe invasive code, and for now i'm keeping off it. :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
