2017-07-21 5:38 GMT+09:00 Cedric BAIL :
> Hi,
>
> On Sun, Jul 16, 2017 at 7:19 PM, Jean-Philippe André
> wrote:
> > I spotted 3 new APIs in evas object:
> >
> > efl_canvas_object.eo.legacy.h, libevas.so.1.20.0
> > evas_object_pointer_coords_inside_get (
Hi,
On Sun, Jul 16, 2017 at 7:19 PM, Jean-Philippe André wrote:
> I spotted 3 new APIs in evas object:
>
> efl_canvas_object.eo.legacy.h, libevas.so.1.20.0
> evas_object_pointer_coords_inside_get ( Efl_Canvas_Object* obj, int x, int
> y )
>
Cedric, Mike,
Could you please comment on JP's review.
We are in beta3 now and if we need to fix some new API it is now.
On 07/17/2017 04:19 AM, Jean-Philippe André wrote:
Hi,
Cedric, Mike,
I spotted 3 new APIs in evas object:
efl_canvas_object.eo.legacy.h, libevas.so.1.20.0
Hi,
Cedric, Mike,
I spotted 3 new APIs in evas object:
efl_canvas_object.eo.legacy.h, libevas.so.1.20.0
evas_object_pointer_coords_inside_get ( Efl_Canvas_Object* obj, int x, int
y )
evas_object_pointer_inside_by_device_get ( Efl_Canvas_Object const* obj,
Efl_Input_Device* dev )
Hello.
On 07/13/2017 02:41 PM, Stefan Schmidt wrote:
Hello.
On 07/07/2017 04:40 PM, Stefan Schmidt wrote:
I will also look through it next week and run our own checker as it
had slightly different results in the past and I want to be sure be
cover both.
And here is the version from our own
Yup, elm_code stuff is still beta.
Andy
On Thu, 13 Jul 2017 at 13:42, Stefan Schmidt wrote:
> Hello.
>
> On 07/07/2017 04:40 PM, Stefan Schmidt wrote:
> > I will also look through it next week and run our own checker as it had
> > slightly different results in the past
Hello.
On 07/07/2017 04:40 PM, Stefan Schmidt wrote:
I will also look through it next week and run our own checker as it had
slightly different results in the past and I want to be sure be cover both.
And here is the version from our own checker scripts:
Hello.
On 07/07/2017 04:40 PM, Stefan Schmidt wrote:
Hello.
Andrey V. Ponomarenko from ABI Laboratory keeps up the great work of
running his tools on EFL on a regular basis.
For the upcoming 1.20 release he has reports for all changes between
1.19.1 and 1.20-beta1
2017-07-10 13:30 GMT+09:00 Andrew Williams :
> I'm curious as to why we've gone from named types back to primitive - is
> this just for C bindings?
>
I was in fact curious as to why we have typedefs for int. IMHO it in fact
harmed readability as you wouldn't know if the
On Mon, 10 Jul 2017 04:30:02 + Andrew Williams said:
> I'm curious as to why we've gone from named types back to primitive - is
> this just for C bindings?
Evas_Coord was used because initially evas had a compile option to have doubles
for coords instead of int's. i
I'm curious as to why we've gone from named types back to primitive - is
this just for C bindings?
Andy
On Mon, 10 Jul 2017 at 03:56, Jean-Philippe André wrote:
> Hi,
>
> 2017-07-08 0:32 GMT+09:00 Andrew Williams :
>
> > It looks like some eo change
Hi,
2017-07-08 0:32 GMT+09:00 Andrew Williams :
> It looks like some eo change moved many Evas_Coord to int - is that correct
> or did we miss something?
>
I changed that in commit af3cb1018584e3c403024b.
ABI wise this doesn't change anything at all.
Since the legacy APIs
It looks like some eo change moved many Evas_Coord to int - is that correct
or did we miss something?
Andy
On Fri, 7 Jul 2017 at 10:41, Stefan Schmidt wrote:
> Hello.
>
> Andrey V. Ponomarenko from ABI Laboratory keeps up the great work of
> running his tools on EFL on a
Hello.
Andrey V. Ponomarenko from ABI Laboratory keeps up the great work of
running his tools on EFL on a regular basis.
For the upcoming 1.20 release he has reports for all changes between
1.19.1 and 1.20-beta1
https://abi-laboratory.pro/tracker/timeline/efl/
14 matches
Mail list logo