On Thu, Jul 30, 2009 at 7:17 AM, Christopher Michael<[email protected]> wrote: > Gustavo Sverzut Barbieri wrote: >> I hate replying to myself, but I clearly missed an important thing >> here: making the Evas_Smart_Class have a pointer to parent, that way >> we basically solve the problem of copying callback definitions as we >> can walk ->parent and check it there. It will also help calling the >> parent methods, for example users of "clipped smart object" need to >> call original "del" method and to do so it need to keep the copy of >> the original method, this way we just sc->parent->del(o) >> >> Of course it adds a bit of overhead of walking the hierarchy, but it >> shouldn't matter much as it should not be that deep/long. >> > > "Should" being the operative word !! What's to stop someone from overloading > ???
you mean: people can get crazy and suddenly come with 1000 levels of inheritance? Well I guess even 1000 is not that much of impact, but supposing it is, we can just recommend doing something else. And we can cache chose in Evas_Smart creation (evas_smart_new()), providing a copy of all signals merged + sorted to speed up access using binary search. But this can easily happen in other ways, for example if you add thousand objects to a single layer, things will get slower, you have to live with it :-) -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: [email protected] Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
