On 8 September 2016 at 21:40, Christopher Michael
wrote:
> On 09/07/2016 06:55 PM, Carsten Haitzler wrote:
> > On Wed, 07 Sep 2016 13:52:40 -0400 Christopher Michael <
> cp.mich...@samsung.com>
> > said:
> >
> >> I would appear that commit 405680e836eb47d7dd8f59a4761386e7a80d9244
> >> changed the
On 09/07/2016 06:55 PM, Carsten Haitzler wrote:
> On Wed, 07 Sep 2016 13:52:40 -0400 Christopher Michael
>
> said:
>
>> I would appear that commit 405680e836eb47d7dd8f59a4761386e7a80d9244
>> changed the way that hold events are sent. They are no longer being sent
>> to the child objects, but rath
On Wed, 07 Sep 2016 13:52:40 -0400 Christopher Michael
said:
> I would appear that commit 405680e836eb47d7dd8f59a4761386e7a80d9244
> changed the way that hold events are sent. They are no longer being sent
> to the child objects, but rather the main 'obj':
>
> -EV_CALL(eo_child, child,
I would appear that commit 405680e836eb47d7dd8f59a4761386e7a80d9244
changed the way that hold events are sent. They are no longer being sent
to the child objects, but rather the main 'obj':
-EV_CALL(eo_child, child, EVAS_CALLBACK_HOLD, ev, event_id, he,
parent_he);
+evas_object_
On Thu, 25 Nov 2010 16:53:08 -0200 Tiago Falcão said:
this would piss a lot of people off if we did it. as such just ASSUMING same
content given 2 structs is wrong - if we had some form of inheritance then yes
- it'd be valid to do so, but really at this stage, i think it's too late in
the game t
Hi,
Before the release, can't reorder these variables to able access as
common fields? (Or inheritance)
Some times I need read event_flags without know if is mouse or key event.
Common Evas_Event:
void *data;
Evas_Modifier *modifiers;//Evas_Event_Hold hasn't
Evas_Lock *l
