Dear Tom,
> What do you think about removing this from upstream and moving it to your
> code?
=> My answer is I really need touch event in the evas.
Yes, it just unifies mouse/multi event and it was in my code before.
However, I think it is better to move that code to the evas, because it is
useful to process event on the touch device(which supports multi fingers), and
other application developers can use that if it is supported by evas.
Other plaform (gtk, iphone, android) already have their own touch event and
they don't have to unify mouse events.
So, I want that evas supports touch event like other platform, and I made a
patch for that.
BR,
Eunmi Lee
------- Original Message -------
Sender : Tom Hacohen<[email protected]> Engineer/STRI-SLP RTL
Language supporting/삼성전자
Date : 2011-10-06 16:17 (GMT+09:00)
Title : Re: [E-devel] [Patch] Evas touch event patch.
On 06/10/11 04:32, EunMi Lee wrote:
> Dear Tom,
>
> Thanks for reporting that issue :)
> I could not think about event_flags problem when I add touch event.
> So, I'm trying to solve that problem and I'd like to share my idea.
>
> The basic idea is "connecting event_flags between mouse(multi) event and
> touch event".
> Actually touch event comes from mouse(multi) event, so I think they can be
> connected.
> - touch down comes from mouse down and multi down.
> - touch move comes from mouse move and multi move.
> - touch up comes from mouse up and multi up.
>
> In the current code, mouse(multi) event is sent to all object and then touch
> event is sent to the all object again.
> I think we can send mouse(multi) event and touch event at a time for one
> object.
> It means, "send mouse(multi) event to the first object and then send touch
> event to the first object, and repeat that for all objects"
> If it is done, I think I can add event_flags for touch event and then pass
> event_flags from mouse(multi) event to touch event and pass to the
> mouse(multi) event again.
> I will be brief as follows:
> ----------------------------------------------
> set mouse/multi event's event_flags to the touch event's one.
> send touch event to the object with event_flags.
> set changed touch event's event_flags to the mouse/multi event's event_flags.
> -----------------------------------------------
>
I think it'll work, with emphasis on sending it one level at a time (i.e
one object at a time) because otherwise you depend on what comes first,
mouse_down or touch_event.
The real question is: do you really need it? What we did to overcome the
lack of a unified object in gesture_layer was "normalizing" input
events. We just created our own touch_event internally, and converted
mouse_down/multi_down (or any other event) to them, only in our code.
What do you think about removing this from upstream and moving it to
your code?
Everyone else: what do you think?
--
Tom.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
