Nathan Ingersoll wrote:
Oh, by splitting it up, I meant to take the specific portions that belong to different engines and separating them, so that they can be called in the realize callback for the windows and only register events for the specific engine being used.
Nathan, I'm a little confused. Ewl_Window inherits from Ewl_Embed, so as far as I can see, this duplicate callback registration should be affecting Ewl_Window as well? I'm not using Ewl_Window, so I wouldn't have noticed...
Currently, EWL registers its ecore callbacks in ewl_ev_init, called from ewl_init. Ewl_Embed registers its evas callbacks in ewl_embed_realize_cb, resulting in duplicate mouse_down/up (etc) events. Doesn't ewl_embed_realize_cb get called even for Ewl_Windows?
If so, then might it be better to do all of this registration from ewl_embed_realize_cb, but conditionally detecting whether we are a genuine embed (i.e. ewl_embed_evas_set has been called)?
-- Simon Poole www.appliancestudio.com ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
