Hello people, As you know, evas_object_show() and evas_object_hide() control visibility for Evas_Object's, and when these are called on one, the respective callbacks (EVAS_CALLBACK_SHOW/HIDE) are triggered.
Now, this works fine if we want to know when an object is supposed to be shown or not, but not when something else controls its visibility, like clippers do. In this case, we need to do all kinds of checks of who clips whom, when alpha is 0, etc, just to know if a certain object is actually visible on screen or not. Since Evas does all this things internally and it can notify users of this kind of changes, doesn't it make sense to have EVAS_CALLBACK_REALIZED and EVAS_CALLBACK_UNREALIZED to track them? Regards, me ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
