I've been playing around with the smart objects in evas a bit, and found something that I think would be nice to have (but haven't thought of any cons yet), so i'll run it by here first.
I think if you set a callback on a smart object it should put that callback on all of the objects that are members (but pass the smart object to the callback). This way people can add their own callbacks for normal evas events to a smart object as a whole. For instance, if we have button widget, why have special handlers to wrap the down, in, out, etc events? (special handlers would still exist to add callbacks for things like a toggle button changing) So, are there any pitfalls to having general callbacks on smart objects? Or does this sound like a good idea? -- brian ------------------------------------------------------- This SF.NET email is sponsored by: Thawte.com Understand how to protect your customers personal information by implementing SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en _______________________________________________ enlightenment-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
