[meta-freescale] Yacto rootfs: multi-touch message cannot handled by "close" button

Duan Fugang-B38611 B38611 at freescale.com
Thu Sep 26 18:57:51 PDT 2013


Hi Ross, peter,

How about your idea for the issue ?

Thanks,
Andy

> -----Original Message-----
> From: Duan Fugang-B38611
> Sent: Thursday, September 26, 2013 5:19 PM
> To: 'Burton, Ross'
> Cc: peter.hutterer at who-t.net; Rutledge Shawn; meta-
> freescale at yoctoproject.org
> Subject: RE: Yacto rootfs: multi-touch message cannot handled by
> "close" button
> 
> From: Burton, Ross [mailto:ross.burton at intel.com]
> Data: Thursday, September 26, 2013 4:51 PM
> 
> > To: Duan Fugang-B38611
> > Cc: peter.hutterer at who-t.net; Rutledge Shawn; meta-
> > freescale at yoctoproject.org
> > Subject: Re: Yacto rootfs: multi-touch message cannot handled by
> > "close" button
> >
> > On 26 September 2013 09:46, Duan Fugang-B38611 <B38611 at freescale.com>
> > wrote:
> > > Ross, thanks for your quick response.
> > >
> > > Why the touch can be recognized in the single  touch mode ? Since
> the
> > > driver is similar the same except report event types.
> > >
> > > And, how to validate whether the touch can be recognized ?
> >
> > I don't know why it can't be recognised in multitouch, and unless you
> > send me your hardware I can't tell you.  That's what we're attempting
> > to debug over email.
> >
> My hardware:
> Board: Imx6q sabresd
> Touchscreen: hannStar display with egalax i2c touchscreen
> 
> 
> > As far as xev is concerned there should be zero difference between
> > using a mouse to click in the window, and using the touchscreen.  Try
> > all combinations of pressing/clicking in the xev window, and report
> > back.
> >
> > Ross
> 
> For EGALAX MULTI TOUCH:
> o	When click the “X” icon to close window,  the window cannot be
> closed, and print the log: (picture #1)
> 	LeaveNotify event, serial 28, synthetic NO, window 0x1000001,
>     	root 0xc2, subw 0x0, time 347181500, (981,-34), root:(981,14),
>     	mode NotifyNormal, detail NotifyNonlinear, same_screen YES,
>     	focus YES, state 0
> 
> o	When click the control bar: (picture #2)
> 	LeaveNotify event, serial 28, synthetic NO, window 0x1000001,
>     	root 0xc2, subw 0x0, time 348522728, (375,-26), root:(375,22),
>     	mode NotifyNormal, detail NotifyNonlinear, same_screen YES,
>     	focus YES, state 0
> 
> o	When click the blank region: (picture #3)
> 	MotionNotify event, serial 28, synthetic NO, window 0x1000001,
>     	root 0xc2, subw 0x0, time 348582340, (289,92), root:(289,140),
>     	state 0x0, is_hint 0, same_screen YES
> 
> 	ButtonPress event, serial 28, synthetic NO, window 0x1000001,
>     	root 0xc2, subw 0x0, time 348582340, (289,92), root:(289,140),
>     	state 0x100, button 1, same_screen YES
> 
> 	ButtonRelease event, serial 28, synthetic NO, window 0x1000001,
>     	root 0xc2, subw 0x0, time 348582619, (289,92), root:(289,140),
>     	state 0x100, button 1, same_screen YES
> 
> o	When click the other icons on the control bar, work fine and
> there have sub-window pop: (picture #4)
> 	FocusOut event, serial 28, synthetic NO, window 0x1000001,
>     	mode NotifyGrab, detail NotifyNonlinear
> 
> 	VisibilityNotify event, serial 28, synthetic NO, window 0x1000001,
>     	state VisibilityPartiallyObscured
> 
> All other operations are right, only clicking "X" icon cannot close the
> windows.
> 
> Thanks,
> Andy


More information about the meta-freescale mailing list