OK, let me describe more about what I want to do :] There are some gestures have to send touch events directly to the activated window on the mobile device. Those are 1 finger double tap and hold for the drag and drop, and 2 fingers swipe for the scrolling (could be used for pinch zoom).
I could not use ecore_x_mouse_* family because of the Wayland environment. The role of gesture recognition moved into the Enlightenment module. The module needs to send touch events for above cases. Um, or the module might have to send the touch evnets information using IPC, then an activated window should generate the proper touch events based on the received information. It should take care of drad and drop window (changed activated window while drag and drop) 2016. 4. 21. 오후 8:05에 "Lukasz Stanislawski" <[email protected]>님이 작성: > On 21.04.2016 08:54, Carsten Haitzler (The Rasterman) wrote: > > On Thu, 21 Apr 2016 15:24:46 +0900 Kim Shinwoo <[email protected]> > said: > > > >> Dear All, Hello. > >> I'm using a ecore_event_filter to recognize some gestures for the screen > >> reader on the Enlightenment module. > >> I have to add Ecore_Event_Mouse_* event in the ecore_event_filter for > some > >> gestures. When I added an event in the ecore_event_filter, this > >> ecore_event_filter got the added event also. So I need to distinguish > newly > >> added event. > >> What is proper way? Can I add a flag to Ecore_Event_Mouse_* such as.. > >> unsigned char is_accessibility: 1; > >> > >> Thank you for enlightening me in advace :P > > this smells totally wrong for some reason. with atspi accessibility is > done by > > dbus and high level protocol... so why this faking of events? > > > > you can determine you made the event by storing the event pointers and > matching > > them up to currently "int he queue, not freed yet" event ptrs. at least > ecore > > events. > This sounds exactly as a hack I made for key events in > elm_atspi_bridge.c, so no need to add extra fields for one thing only. > > The reason for this craziness was the atspi requirement. It assumed that > every key event should go like through middle man: > X11 -> App -> Atspi daemon -> App > >> Sincerely, > >> Shinwoo Kim. > >> > ------------------------------------------------------------------------------ > >> Find and fix application performance issues faster with Applications > Manager > >> Applications Manager provides deep performance insights into multiple > tiers of > >> your business applications. It resolves application problems quickly and > >> reduces your MTTR. Get your free trial! > >> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > >> _______________________________________________ > >> enlightenment-devel mailing list > >> [email protected] > >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > >> > > > > > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications > Manager > Applications Manager provides deep performance insights into multiple > tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
