On 8/20/07, Brett Nash <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-08-21 at 00:58 +0200, Simon TRENY wrote:
> > Hi,
> >
> > I've seen in Evas.h that most of the methods of Evas_Smart_Class are
> > marked as to-be-deleted in the future ("FIXME: DELETE ME"). This
> > concerns show(), hide(), color_set(), clip_set() and clip_unset().
> >
> > I think it will be indeed a really great thing to do since when we
> > implement these methods for a new smart-object, we basically always do
> > the same thing (i.e clipping member-objects against the parent's
> > clipper in clip_set(), hiding the member-objects in hide_set()...).
>
> I disagree here.  You are correct in that 95+% of cases are just
> hide/show the clip and the like.  However we have a number of widgets
> that do things like stop animations, release resources or similar
> actions on hide calls, also more complex widgets delay layout
> recalculations until the show call.
>
> However being able to set the calls to NULL, and allow evas to do the
> obvious things in these cases.

evas_object_event_callback_add()?

-- 
Gustavo Sverzut Barbieri
--------------------------------------
Jabber: [EMAIL PROTECTED]
   MSN: [EMAIL PROTECTED]
  ICQ#: 17249123
 Skype: gsbarbieri
Mobile: +55 (81) 9927 0010

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to