Re: [E-devel] Evas_Event_Mouse_Move missing data

2017-07-12 Thread Andrew Williams
Hi, It may be specific to OS X as that's what I was using yesterday - will get more info if I can today. Thanks, Andy On Wed, 12 Jul 2017 at 03:48, Jean-Philippe André wrote: > I couldn't reproduce that with today's git. > Can you provide me with some test code? Maybe in

Re: [E-devel] Evas_Event_Mouse_Move missing data

2017-07-11 Thread Jean-Philippe André
I couldn't reproduce that with today's git. Can you provide me with some test code? Maybe in EDI? 2017-07-12 4:57 GMT+09:00 Andrew Williams : > Hi, > > Thanks for the help - I will test it shortly. > Unfortunately I have also found that Mouse_Wheel data structures always >

Re: [E-devel] Evas_Event_Mouse_Move missing data

2017-07-11 Thread Andrew Williams
Hi, Thanks for the help - I will test it shortly. Unfortunately I have also found that Mouse_Wheel data structures always seem to have canvas.x and .y are always 0 :( I assume this is a different issue as it's broken on git master. Thanks, Andy On Mon, 10 Jul 2017 at 08:04 Jean-Philippe André

Re: [E-devel] Evas_Event_Mouse_Move missing data

2017-07-10 Thread Jean-Philippe André
Hi Andy, 2017-07-10 11:56 GMT+09:00 Jean-Philippe André : > > > > 2017-07-09 2:19 GMT+09:00 Andrew Williams : > >> Hi, >> >> I was trying to use a mouse_move event earlier but found it was missing >> critical info: >> >> event->buttons >>

Re: [E-devel] Evas_Event_Mouse_Move missing data

2017-07-09 Thread Jean-Philippe André
2017-07-09 2:19 GMT+09:00 Andrew Williams : > Hi, > > I was trying to use a mouse_move event earlier but found it was missing > critical info: > > event->buttons > event->prev.canvas.x > event->prev.canvas.y > > Were always 0. > Am I missing something obvious? I had to code

[E-devel] Evas_Event_Mouse_Move missing data

2017-07-08 Thread Andrew Williams
Hi, I was trying to use a mouse_move event earlier but found it was missing critical info: event->buttons event->prev.canvas.x event->prev.canvas.y Were always 0. Am I missing something obvious? I had to code up the gesture using mouse_down/up to capture the missing info instead... Thanks,