ore id=2 x=580 y=67
>> >> >> eCore id=1 x=153 y=56
>> >> >> eCore id=1 x=153 y=57
>> >> >> eCore id=1 x=152 y=57
>> >> >> eCore id=2 x=580 y=68
>> >> >> eCore id=2 x=581 y=68
>> >> >>
>>
Core id=1 x=153 y=57
> >> >> eCore id=1 x=152 y=57
> >> >> eCore id=2 x=580 y=68
> >> >> eCore id=2 x=581 y=68
> >> >>
> >> >>
> >> >> this is where my problem is,a lot of ecore events are generated but on
> &
>
>> >> I couldn't find why some events are not reflected in evas_callbacks.
>> >>
>> >> is there a way to process the touch events as a seperate thread in
>> >> ecore_event_procesing? or any other solution for this problem?
>> >
&
y other solution for this problem?
> >
> > threads have nothing to do with this other than complicating things. they
> > don't solve anything, and won't. (unless u are spending large amounts of
> > cpu just handling the input event stream and making ecore events
input event stream and making ecore events out of it). so you
> get
> ecore events - fine, but evas isnt calling back for all events... that
> shouldn't happen (unless position hasn't changed etc.)
>
>> Regards
>> HariHaraSudhan
>>
>> On Thu, Nov 3, 2011 at
vents - fine, but evas isnt calling back for all events... that
shouldn't happen (unless position hasn't changed etc.)
> Regards
> HariHaraSudhan
>
> On Thu, Nov 3, 2011 at 6:34 PM, HariHara Sudhan wrote:
> > Sent from my Windows Phone
> > From: Carsten Haitzler
r any other solution for this problem?
Regards
HariHaraSudhan
On Thu, Nov 3, 2011 at 6:34 PM, HariHara Sudhan wrote:
> Sent from my Windows Phone
> From: Carsten Haitzler
> Sent: 11/3/2011 4:20 PM
> To: Enlightenment developer list
> Cc: HariHara Sudhan
> Subject: Re: [E-devel]
On Wed, 2 Nov 2011 19:38:09 +0530 HariHara Sudhan said:
> Hi all,
> I've lately added mtdev to receive touch events and process them as
> ecore mouse events( as mpx).
> i get the window id by the original mouse movements and use that id
> for passing touch events for that window.
>
> i get the s
Hi all,
I've lately added mtdev to receive touch events and process them as
ecore mouse events( as mpx).
i get the window id by the original mouse movements and use that id
for passing touch events for that window.
i get the slot id from mtdev. Passing the slot id(starting from 1)
makes ecore thin
