The duplication doesn't happen because Ewl_Window does not feed the
events through evas.
Maybe we should just add a parameter to ewl_embed_evas_set to flag if
it should register evas events or not. I believe the window uses that
API call to set it's evas too.
On 6/17/05, Simon Poole <[EMAIL PROTE
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 confus
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.
Ah, I get it. Would make s
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.
This patch will be just fine until someone gets around
Nathan Ingersoll wrote:
Well that's a pain. I think the callback registration may need to be
moved to the ewl_window to avoid that situation. The idea is that the
FB event handlers are used when an EWL application has control of the
FB, and the evas object events are for when the EWL object is pl
Well that's a pain. I think the callback registration may need to be
moved to the ewl_window to avoid that situation. The idea is that the
FB event handlers are used when an EWL application has control of the
FB, and the evas object events are for when the EWL object is placed
on a pre-existing eva
I'm getting two EWL_CALLBACK_CLICKED events for every button click in my
ewl_embed (running in a framebuffer Evas). I think this is happening
because EWL is registering twice to receive mouse events:
1. ecore_event_handler_add(ECORE_FB_EVENT...) in ewl_ev_init(),
called from ewl_init().
2
