* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
@ 2013-09-26 8:21 Duan Fugang-B38611
2013-09-26 8:25 ` Burton, Ross
0 siblings, 1 reply; 24+ messages in thread
From: Duan Fugang-B38611 @ 2013-09-26 8:21 UTC (permalink / raw)
To: peter.hutterer@who-t.net
Cc: meta-freescale@yoctoproject.org, Rutledge Shawn,
ross.burton@intel.com
[-- Attachment #1.1: Type: text/plain, Size: 5079 bytes --]
Hi, Peter,
Firstly, I am sorry to reply the email in informality rules, which is conveniency for me to explain the issue.
I use the xev tool to validate events.
Ø For EGALAX SINGLE TOUCH:
o When click the "X" icon to close window, the window can be closed, and print the log:
LeaveNotify event, serial 28, synthetic NO, window 0x1000001,
root 0xc2, subw 0x0, time 347162489, (983,-35), root:(983,13),
mode NotifyNormal, detail NotifyNonlinear, same_screen YES,
focus YES, state 0
ClientMessage event, serial 28, synthetic YES, window 0x1000001,
message_type 0x109 (WM_PROTOCOLS), format 32, message 0x107 (WM_DELETE_WINDOW)
Ø For EGALAX MULTI TOUCH:
o When click the "X" icon to close window, the window cannot be closed, and print the log:
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
Ø Other event operations are correctly handled for both SINGLE and MULTI touch.
So, issue: why there have no "ClientMessage event" for EGALAX MULTI TOUCH ?
[cid:image001.png@01CEBAD3.5A59E670]
Thanks,
Andy
From: Peter Hutterer [mailto:peter.hutterer@who-t.net]
Sent: Wednesday, September 25, 2013 2:31 AM
To: Duan Fugang-B38611
Subject: Re: Yacto rootfs: multi-touch message cannot handled by "close" button
On Tue, Sep 24, 2013 at 08:35:46AM +0000, Duan Fugang-B38611 wrote:
> Hi, Peter,
>
> We use the X.Org X Server 1.14.0 + QT4.8.5 to do one demo, but I catch one issue: multi-touch message is not handled by "close" button.
>
> I use egalax touchscreen for the multi-touch test.
> After kernel up, evtest test the multi-touch message, all pass. Use xinput to do the test, also pass.
>
> Open one QT app, all multi-touch message can be processed, but the window of the app cannot be closed by click the "X" icon in the right-up region.
> I test GNOME destop with the same kernel, any apps' window can be closed.
>
> So, It is strange, maybe it is KDE issue for multi-touch ? Or mtdev / edev issue for multi-touch ?
i'm pretty sure this is a QT issue, especially if you say that GNOME works fine. run xev to see if you get a button event from the touch. if you do, then it's probably not a server bug.
Cheers,
Peter
> Current KDE is matchbox-window-manager.
> Current multi-touch support messages:
> root@imx6qsabresd:/# mtdev-test /dev/input/event0 supported mt events:
> ABS_MT_TOUCH_MAJOR
> ABS_MT_WIDTH_MAJOR
> ABS_MT_POSITION_X
> ABS_MT_POSITION_Y
> ABS_MT_TRACKING_ID
>
> Xorg.0.log:
> [347101.123] (II) config/udev: Adding input device eGalax Touch Screen
> (/dev/input/event0) [347101.123] (**) eGalax Touch Screen: Applying InputClass "evdev touchscreen catchall"
> [347101.123] (II) Using input driver 'evdev' for 'eGalax Touch Screen'
> [347101.123] (**) eGalax Touch Screen: always reports core events
> [347101.123] (**) evdev: eGalax Touch Screen: Device: "/dev/input/event0"
> [347101.123] (II) evdev: eGalax Touch Screen: Using mtdev for this
> device [347101.123] (--) evdev: eGalax Touch Screen: Vendor 0xeef
> Product 0x20 [347101.123] (--) evdev: eGalax Touch Screen: Found
> absolute axes [347101.123] (--) evdev: eGalax Touch Screen: Found
> absolute multitouch axes [347101.123] (II) evdev: eGalax Touch Screen: No buttons found, faking one.
> [347101.124] (--) evdev: eGalax Touch Screen: Found x and y absolute
> axes [347101.124] (--) evdev: eGalax Touch Screen: Found absolute
> touchscreen [347101.124] (II) evdev: eGalax Touch Screen: Configuring
> as touchscreen [347101.124] (**) evdev: eGalax Touch Screen:
> YAxisMapping: buttons 4 and 5 [347101.124] (**) evdev: eGalax Touch
> Screen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [347101.124] (**) Option "config_info" "udev:/sys/devices/soc0/soc.1/2100000.aips-bus/21a8000.i2c/i2c-2/2-0004/input/input0/event0"
> [347101.124] (II) XINPUT: Adding extended input device "eGalax Touch
> Screen" (type: TOUCHSCREEN, id 8) [347101.124] (II) evdev: eGalax Touch Screen: initialized for absolute axes..
> [347101.126] (**) eGalax Touch Screen: (accel) keeping acceleration
> scheme 1 [347101.126] (**) eGalax Touch Screen: (accel) acceleration
> profile 0 [347101.126] (**) eGalax Touch Screen: (accel) acceleration
> factor: 2.000 [347101.126] (**) eGalax Touch Screen: (accel)
> acceleration threshold: 4 [347101.127] (II) config/udev: Adding input
> device eGalax Touch Screen (/dev/input/mouse0) [347101.127] (II) No input driver specified, ignoring this device.
> [347101.127] (II) This device may have been added with another device file.
>
> Thanks,
> Andy
[-- Attachment #1.2: Type: text/html, Size: 15427 bytes --]
[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 159385 bytes --]
^ permalink raw reply [flat|nested] 24+ messages in thread* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-26 8:21 Yacto rootfs: multi-touch message cannot handled by "close" button Duan Fugang-B38611
@ 2013-09-26 8:25 ` Burton, Ross
2013-09-26 8:46 ` Duan Fugang-B38611
0 siblings, 1 reply; 24+ messages in thread
From: Burton, Ross @ 2013-09-26 8:25 UTC (permalink / raw)
To: Duan Fugang-B38611
Cc: meta-freescale@yoctoproject.org, peter.hutterer@who-t.net,
Rutledge Shawn
[-- Attachment #1: Type: text/plain, Size: 366 bytes --]
On 26 September 2013 09:21, Duan Fugang-B38611 <B38611@freescale.com> wrote:
> *So, issue: why there have no “ClientMessage event” for EGALAX MULTI
> TOUCH ?*
>
>
You don't get a ClientMessage event because the touch isn't being
recognised, but you didn't verify that touches are being recognised
correctly. Tap inside the xev window itself.
Ross
[-- Attachment #2: Type: text/html, Size: 862 bytes --]
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-26 8:25 ` Burton, Ross
@ 2013-09-26 8:46 ` Duan Fugang-B38611
2013-09-26 8:51 ` Burton, Ross
0 siblings, 1 reply; 24+ messages in thread
From: Duan Fugang-B38611 @ 2013-09-26 8:46 UTC (permalink / raw)
To: Burton, Ross
Cc: meta-freescale@yoctoproject.org, peter.hutterer@who-t.net,
Rutledge Shawn
[-- Attachment #1: Type: text/plain, Size: 708 bytes --]
On Sep 26, 2013 at 04:26pM, Ross ross.burton@intel.com<mailto:ross.burton@intel.com> wrote:
>On 26 September 2013 09:21, Duan Fugang-B38611 <B38611@freescale.com> wrote:
>So, issue: why there have no “ClientMessage event” for EGALAX MULTI TOUCH ?
>
>You don't get a ClientMessage event because the touch isn't being recognised, but you didn't verify that touches are being recognised correctly. Tap inside the xev window itself.
>
>Ross
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 ?
Thanks very much!
Andy
[-- Attachment #2: Type: text/html, Size: 5098 bytes --]
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-26 8:46 ` Duan Fugang-B38611
@ 2013-09-26 8:51 ` Burton, Ross
2013-09-26 9:19 ` Duan Fugang-B38611
` (2 more replies)
0 siblings, 3 replies; 24+ messages in thread
From: Burton, Ross @ 2013-09-26 8:51 UTC (permalink / raw)
To: Duan Fugang-B38611
Cc: meta-freescale@yoctoproject.org, peter.hutterer@who-t.net,
Rutledge Shawn
On 26 September 2013 09:46, Duan Fugang-B38611 <B38611@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.
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
^ permalink raw reply [flat|nested] 24+ messages in thread* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-26 8:51 ` Burton, Ross
@ 2013-09-26 9:19 ` Duan Fugang-B38611
2013-09-26 9:25 ` Duan Fugang-B38611
2013-09-27 1:57 ` Duan Fugang-B38611
2 siblings, 0 replies; 24+ messages in thread
From: Duan Fugang-B38611 @ 2013-09-26 9:19 UTC (permalink / raw)
To: Burton, Ross
Cc: meta-freescale@yoctoproject.org, peter.hutterer@who-t.net,
Rutledge Shawn
[-- Attachment #1: Type: text/plain, Size: 2790 bytes --]
From: Burton, Ross [mailto:ross.burton@intel.com]
Data: Thursday, September 26, 2013 4:51 PM
> To: Duan Fugang-B38611
> Cc: peter.hutterer@who-t.net; Rutledge Shawn; meta-
> freescale@yoctoproject.org
> Subject: Re: Yacto rootfs: multi-touch message cannot handled by
> "close" button
>
> On 26 September 2013 09:46, Duan Fugang-B38611 <B38611@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
[-- Attachment #2: 1.jpg --]
[-- Type: image/jpeg, Size: 196497 bytes --]
[-- Attachment #3: 4.bmp --]
[-- Type: image/bmp, Size: 768054 bytes --]
[-- Attachment #4: 2.bmp --]
[-- Type: image/bmp, Size: 768054 bytes --]
[-- Attachment #5: 3.bmp --]
[-- Type: image/bmp, Size: 768054 bytes --]
^ permalink raw reply [flat|nested] 24+ messages in thread* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-26 8:51 ` Burton, Ross
2013-09-26 9:19 ` Duan Fugang-B38611
@ 2013-09-26 9:25 ` Duan Fugang-B38611
2013-09-26 9:45 ` Eric Bénard
2013-09-27 1:57 ` Duan Fugang-B38611
2 siblings, 1 reply; 24+ messages in thread
From: Duan Fugang-B38611 @ 2013-09-26 9:25 UTC (permalink / raw)
To: Burton, Ross
Cc: meta-freescale@yoctoproject.org, peter.hutterer@who-t.net,
Rutledge Shawn
From: Burton, Ross [mailto:ross.burton@intel.com]
Data: Thursday, September 26, 2013 4:51 PM
> To: Duan Fugang-B38611
> Cc: peter.hutterer@who-t.net; Rutledge Shawn; meta-
> freescale@yoctoproject.org
> Subject: Re: Yacto rootfs: multi-touch message cannot handled by
> "close" button
>
> On 26 September 2013 09:46, Duan Fugang-B38611 <B38611@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.
>
> 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
There have some xorg log: (Which shows the touch can be recognized by evdev)
For multi touch:
[347101.119] (II) config/udev: Adding input device eGalax Touch Screen (/dev/input/event0)
[347101.120] (**) eGalax Touch Screen: Applying InputClass "evdev touchscreen catchall"
[347101.120] (II) Using input driver 'evdev' for 'eGalax Touch Screen'
[347101.120] (**) eGalax Touch Screen: always reports core events
[347101.120] (**) evdev: eGalax Touch Screen: Device: "/dev/input/event0"
[347101.120] (II) evdev: eGalax Touch Screen: Using mtdev for this device
[347101.120] (--) evdev: eGalax Touch Screen: Vendor 0xeef Product 0x20
[347101.120] (--) evdev: eGalax Touch Screen: Found absolute axes
[347101.120] (--) evdev: eGalax Touch Screen: Found absolute multitouch axes
[347101.120] (II) evdev: eGalax Touch Screen: No buttons found, faking one.
[347101.120] (--) evdev: eGalax Touch Screen: Found x and y absolute axes
[347101.120] (--) evdev: eGalax Touch Screen: Found absolute touchscreen
[347101.120] (II) evdev: eGalax Touch Screen: Configuring as touchscreen
[347101.120] (**) evdev: eGalax Touch Screen: YAxisMapping: buttons 4 and 5
[347101.120] (**) evdev: eGalax Touch Screen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[347101.120] (**) Option "config_info" "udev:/sys/devices/soc0/soc.1/2100000.aips-bus/21a8000.i2c/i2c-2/2-0004/input/input0/event0"
[347101.120] (II) XINPUT: Adding extended input device "eGalax Touch Screen" (type: TOUCHSCREEN, id 8)
[347101.121] (II) evdev: eGalax Touch Screen: initialized for absolute axes.
[347101.123] (**) eGalax Touch Screen: (accel) keeping acceleration scheme 1
[347101.123] (**) eGalax Touch Screen: (accel) acceleration profile 0
[347101.123] (**) eGalax Touch Screen: (accel) acceleration factor: 2.000
[347101.123] (**) eGalax Touch Screen: (accel) acceleration threshold: 4
[347101.124] (II) config/udev: Adding input device eGalax Touch Screen (/dev/input/mouse0)
For single touch:
[347100.954] (II) config/udev: Adding input device eGalax Touch Screen (/dev/input/event0)
[347100.954] (**) eGalax Touch Screen: Applying InputClass "evdev touchscreen catchall"
[347100.954] (II) Using input driver 'evdev' for 'eGalax Touch Screen'
[347100.954] (**) eGalax Touch Screen: always reports core events
[347100.954] (**) evdev: eGalax Touch Screen: Device: "/dev/input/event0"
[347100.954] (--) evdev: eGalax Touch Screen: Vendor 0xeef Product 0x20
[347100.954] (--) evdev: eGalax Touch Screen: Found absolute axes
[347100.954] (--) evdev: eGalax Touch Screen: Found x and y absolute axes
[347100.954] (--) evdev: eGalax Touch Screen: Found absolute touchscreen
[347100.955] (II) evdev: eGalax Touch Screen: Configuring as touchscreen
[347100.955] (**) evdev: eGalax Touch Screen: YAxisMapping: buttons 4 and 5
[347100.955] (**) evdev: eGalax Touch Screen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[347100.955] (**) Option "config_info" "udev:/sys/devices/soc0/soc.1/2100000.aips-bus/21a8000.i2c/i2c-2/2-0004/input/input0/event0"
[347100.955] (II) XINPUT: Adding extended input device "eGalax Touch Screen" (type: TOUCHSCREEN, id 8)
[347100.955] (II) evdev: eGalax Touch Screen: initialized for absolute axes.
[347100.966] (**) eGalax Touch Screen: (accel) keeping acceleration scheme 1
[347100.966] (**) eGalax Touch Screen: (accel) acceleration profile 0
[347100.967] (**) eGalax Touch Screen: (accel) acceleration factor: 2.000
[347100.967] (**) eGalax Touch Screen: (accel) acceleration threshold: 4
Thanks
Andy
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-26 9:25 ` Duan Fugang-B38611
@ 2013-09-26 9:45 ` Eric Bénard
2013-09-26 13:24 ` Duan Fugang-B38611
0 siblings, 1 reply; 24+ messages in thread
From: Eric Bénard @ 2013-09-26 9:45 UTC (permalink / raw)
To: Duan Fugang-B38611
Cc: meta-freescale@yoctoproject.org, peter.hutterer@who-t.net,
Rutledge Shawn, Burton, Ross
Hi Duan,
Le Thu, 26 Sep 2013 09:25:12 +0000,
Duan Fugang-B38611 <B38611@freescale.com> a écrit :
> There have some xorg log: (Which shows the touch can be recognized by evdev)
>
Ross asked you to launch xev from your console and touch the screen in
the xev window so that you can provide xev's log to understand your
problem.
More info about xev :
http://manpages.ubuntu.com/manpages/hardy/man1/xev.1.html
Eric
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-26 9:45 ` Eric Bénard
@ 2013-09-26 13:24 ` Duan Fugang-B38611
2013-09-26 13:31 ` Eric Bénard
2013-09-30 1:14 ` Peter Hutterer
0 siblings, 2 replies; 24+ messages in thread
From: Duan Fugang-B38611 @ 2013-09-26 13:24 UTC (permalink / raw)
To: Eric Bénard
Cc: meta-freescale@yoctoproject.org, peter.hutterer@who-t.net,
Rutledge Shawn, Burton, Ross
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
From: Eric Bénard [mailto:eric@eukrea.com]
Data: Thursday, September 26, 2013 5:46 PM
> To: Duan Fugang-B38611
> Cc: Burton, Ross; meta-freescale@yoctoproject.org; peter.hutterer@who-
> t.net; Rutledge Shawn
> Subject: Re: [meta-freescale] Yacto rootfs: multi-touch message cannot
> handled by "close" button
>
> Hi Duan,
>
> Le Thu, 26 Sep 2013 09:25:12 +0000,
> Duan Fugang-B38611 <B38611@freescale.com> a écrit :
> > There have some xorg log: (Which shows the touch can be recognized by
> evdev)
> >
> Ross asked you to launch xev from your console and touch the screen in
> the xev window so that you can provide xev's log to understand your
> problem.
>
> More info about xev :
> http://manpages.ubuntu.com/manpages/hardy/man1/xev.1.html
>
> Eric
I had sent out the test result as the previous email as attached mail.
Thanks,
Andy
[-- Attachment #2: Type: message/rfc822, Size: 3473690 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 2901 bytes --]
From: Burton, Ross [mailto:ross.burton@intel.com]
Data: Thursday, September 26, 2013 4:51 PM
> To: Duan Fugang-B38611
> Cc: peter.hutterer@who-t.net; Rutledge Shawn; meta-
> freescale@yoctoproject.org
> Subject: Re: Yacto rootfs: multi-touch message cannot handled by
> "close" button
>
> On 26 September 2013 09:46, Duan Fugang-B38611 <B38611@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
[-- Attachment #2.1.2: 1.jpg --]
[-- Type: image/jpeg, Size: 229428 bytes --]
[-- Attachment #2.1.3: 4.bmp --]
[-- Type: image/bmp, Size: 768054 bytes --]
[-- Attachment #2.1.4: 2.bmp --]
[-- Type: image/bmp, Size: 768054 bytes --]
[-- Attachment #2.1.5: 3.bmp --]
[-- Type: image/bmp, Size: 768054 bytes --]
^ permalink raw reply [flat|nested] 24+ messages in thread* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-26 13:24 ` Duan Fugang-B38611
@ 2013-09-26 13:31 ` Eric Bénard
2013-09-26 13:33 ` Duan Fugang-B38611
2013-09-30 1:14 ` Peter Hutterer
1 sibling, 1 reply; 24+ messages in thread
From: Eric Bénard @ 2013-09-26 13:31 UTC (permalink / raw)
To: Duan Fugang-B38611
Cc: meta-freescale@yoctoproject.org, peter.hutterer@who-t.net,
Rutledge Shawn, Burton, Ross
Le Thu, 26 Sep 2013 13:24:59 +0000,
Duan Fugang-B38611 <B38611@freescale.com> a écrit :
> From: Eric Bénard [mailto:eric@eukrea.com]
> Data: Thursday, September 26, 2013 5:46 PM
>
> > To: Duan Fugang-B38611
> > Cc: Burton, Ross; meta-freescale@yoctoproject.org; peter.hutterer@who-
> > t.net; Rutledge Shawn
> > Subject: Re: [meta-freescale] Yacto rootfs: multi-touch message cannot
> > handled by "close" button
> >
> > Hi Duan,
> >
> > Le Thu, 26 Sep 2013 09:25:12 +0000,
> > Duan Fugang-B38611 <B38611@freescale.com> a écrit :
> > > There have some xorg log: (Which shows the touch can be recognized by
> > evdev)
> > >
> > Ross asked you to launch xev from your console and touch the screen in
> > the xev window so that you can provide xev's log to understand your
> > problem.
> >
> > More info about xev :
> > http://manpages.ubuntu.com/manpages/hardy/man1/xev.1.html
> >
> > Eric
>
> I had sent out the test result as the previous email as attached mail.
>
I saw that after as the mails arrived in the wrong order here ;-)
Eric
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-26 13:31 ` Eric Bénard
@ 2013-09-26 13:33 ` Duan Fugang-B38611
2013-09-26 15:57 ` Eric Bénard
0 siblings, 1 reply; 24+ messages in thread
From: Duan Fugang-B38611 @ 2013-09-26 13:33 UTC (permalink / raw)
To: Eric Bénard
Cc: meta-freescale@yoctoproject.org, peter.hutterer@who-t.net,
Rutledge Shawn, Burton, Ross
From: Eric Bénard [mailto:eric@eukrea.com]
Data: Thursday, September 26, 2013 9:32 PM
> To: Duan Fugang-B38611
> Cc: Burton, Ross; meta-freescale@yoctoproject.org; peter.hutterer@who-
> t.net; Rutledge Shawn
> Subject: Re: [meta-freescale] Yacto rootfs: multi-touch message cannot
> handled by "close" button
>
> Le Thu, 26 Sep 2013 13:24:59 +0000,
> Duan Fugang-B38611 <B38611@freescale.com> a écrit :
>
> > From: Eric Bénard [mailto:eric@eukrea.com]
> > Data: Thursday, September 26, 2013 5:46 PM
> >
> > > To: Duan Fugang-B38611
> > > Cc: Burton, Ross; meta-freescale@yoctoproject.org;
> peter.hutterer@who-
> > > t.net; Rutledge Shawn
> > > Subject: Re: [meta-freescale] Yacto rootfs: multi-touch message
> cannot
> > > handled by "close" button
> > >
> > > Hi Duan,
> > >
> > > Le Thu, 26 Sep 2013 09:25:12 +0000,
> > > Duan Fugang-B38611 <B38611@freescale.com> a écrit :
> > > > There have some xorg log: (Which shows the touch can be
> recognized by
> > > evdev)
> > > >
> > > Ross asked you to launch xev from your console and touch the screen
> in
> > > the xev window so that you can provide xev's log to understand your
> > > problem.
> > >
> > > More info about xev :
> > > http://manpages.ubuntu.com/manpages/hardy/man1/xev.1.html
> > >
> > > Eric
> >
> > I had sent out the test result as the previous email as attached mail.
> >
> I saw that after as the mails arrived in the wrong order here ;-)
>
> Eric
Ok, do you have any thinking with the issue ?
Thanks,
Andy
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-26 13:24 ` Duan Fugang-B38611
2013-09-26 13:31 ` Eric Bénard
@ 2013-09-30 1:14 ` Peter Hutterer
2013-09-30 2:33 ` Duan Fugang-B38611
1 sibling, 1 reply; 24+ messages in thread
From: Peter Hutterer @ 2013-09-30 1:14 UTC (permalink / raw)
To: Duan Fugang-B38611
Cc: meta-freescale@yoctoproject.org, Rutledge Shawn, Burton, Ross
On Thu, Sep 26, 2013 at 01:24:59PM +0000, Duan Fugang-B38611 wrote:
> From: Eric Bénard [mailto:eric@eukrea.com]
> Data: Thursday, September 26, 2013 5:46 PM
>
> > To: Duan Fugang-B38611
> > Cc: Burton, Ross; meta-freescale@yoctoproject.org; peter.hutterer@who-
> > t.net; Rutledge Shawn
> > Subject: Re: [meta-freescale] Yacto rootfs: multi-touch message cannot
> > handled by "close" button
> >
> > Hi Duan,
> >
> > Le Thu, 26 Sep 2013 09:25:12 +0000,
> > Duan Fugang-B38611 <B38611@freescale.com> a écrit :
> > > There have some xorg log: (Which shows the touch can be recognized by
> > evdev)
> > >
> > Ross asked you to launch xev from your console and touch the screen in
> > the xev window so that you can provide xev's log to understand your
> > problem.
> >
> > More info about xev :
> > http://manpages.ubuntu.com/manpages/hardy/man1/xev.1.html
> >
> > Eric
>
> I had sent out the test result as the previous email as attached mail.
>
> Thanks,
> Andy
> Date: Thu, 26 Sep 2013 09:19:12 +0000
> From: Duan Fugang-B38611 <B38611@freescale.com>
> To: "Burton, Ross" <ross.burton@intel.com>
> CC: "peter.hutterer@who-t.net" <peter.hutterer@who-t.net>, Rutledge Shawn
> <Shawn.Rutledge@digia.com>, "meta-freescale@yoctoproject.org"
> <meta-freescale@yoctoproject.org>
> Subject: RE: Yacto rootfs: multi-touch message cannot handled by "close"
> button
>
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Data: Thursday, September 26, 2013 4:51 PM
>
> > To: Duan Fugang-B38611
> > Cc: peter.hutterer@who-t.net; Rutledge Shawn; meta-
> > freescale@yoctoproject.org
> > Subject: Re: Yacto rootfs: multi-touch message cannot handled by
> > "close" button
> >
> > On 26 September 2013 09:46, Duan Fugang-B38611 <B38611@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.
xev only listens to windows in the white area. the window decorations are
provided by the window manager, which should also handle the event on the
close button. if your WM is QT based, maybe QT has some debugging options
you can enable? I'm not sure off-heart.
you can also look into hooking up systemtap do debug which events are
actually sent by the server, this should at least give you a hint of what
the server does and where the problem lies.
Cheers,
Peter
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-30 1:14 ` Peter Hutterer
@ 2013-09-30 2:33 ` Duan Fugang-B38611
0 siblings, 0 replies; 24+ messages in thread
From: Duan Fugang-B38611 @ 2013-09-30 2:33 UTC (permalink / raw)
To: Peter Hutterer
Cc: meta-freescale@yoctoproject.org, Li Frank-B20596, Rutledge Shawn,
Burton, Ross
From: Peter Hutterer [mailto:peter.hutterer@who-t.net]
Sent: Monday, September 30, 2013 9:14 AM
> To: Duan Fugang-B38611
> Cc: Eric Bénard; Burton, Ross; meta-freescale@yoctoproject.org; Rutledge
> Shawn
> Subject: Re: [meta-freescale] Yacto rootfs: multi-touch message cannot
> handled by "close" button
>
> On Thu, Sep 26, 2013 at 01:24:59PM +0000, Duan Fugang-B38611 wrote:
> > From: Eric Bénard [mailto:eric@eukrea.com]
> > Data: Thursday, September 26, 2013 5:46 PM
> >
> > > To: Duan Fugang-B38611
> > > Cc: Burton, Ross; meta-freescale@yoctoproject.org;
> > > peter.hutterer@who- t.net; Rutledge Shawn
> > > Subject: Re: [meta-freescale] Yacto rootfs: multi-touch message
> > > cannot handled by "close" button
> > >
> > > Hi Duan,
> > >
> > > Le Thu, 26 Sep 2013 09:25:12 +0000,
> > > Duan Fugang-B38611 <B38611@freescale.com> a écrit :
> > > > There have some xorg log: (Which shows the touch can be recognized
> > > > by
> > > evdev)
> > > >
> > > Ross asked you to launch xev from your console and touch the screen
> > > in the xev window so that you can provide xev's log to understand
> > > your problem.
> > >
> > > More info about xev :
> > > http://manpages.ubuntu.com/manpages/hardy/man1/xev.1.html
> > >
> > > Eric
> >
> > I had sent out the test result as the previous email as attached mail.
> >
> > Thanks,
> > Andy
>
> > Date: Thu, 26 Sep 2013 09:19:12 +0000
> > From: Duan Fugang-B38611 <B38611@freescale.com>
> > To: "Burton, Ross" <ross.burton@intel.com>
> > CC: "peter.hutterer@who-t.net" <peter.hutterer@who-t.net>, Rutledge
> > Shawn <Shawn.Rutledge@digia.com>, "meta-freescale@yoctoproject.org"
> > <meta-freescale@yoctoproject.org>
> > Subject: RE: Yacto rootfs: multi-touch message cannot handled by "close"
> > button
> >
> > From: Burton, Ross [mailto:ross.burton@intel.com]
> > Data: Thursday, September 26, 2013 4:51 PM
> >
> > > To: Duan Fugang-B38611
> > > Cc: peter.hutterer@who-t.net; Rutledge Shawn; meta-
> > > freescale@yoctoproject.org
> > > Subject: Re: Yacto rootfs: multi-touch message cannot handled by
> > > "close" button
> > >
> > > On 26 September 2013 09:46, Duan Fugang-B38611
> > > <B38611@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.
>
> xev only listens to windows in the white area. the window decorations are
> provided by the window manager, which should also handle the event on the
> close button. if your WM is QT based, maybe QT has some debugging options
> you can enable? I'm not sure off-heart.
>
Yes, the current WM is based QT.
Thanks for your suggestion.
For single touch, xev can listen the ClientMessage event with message 0x107 (WM_DELETE_WINDOW) when click the "X" to close the window in normally.
For multi touch, xev cannot get the message.
You mean the event is handled by WM, it is matchbox-window-manager issue ?
> you can also look into hooking up systemtap do debug which events are
> actually sent by the server, this should at least give you a hint of what
> the server does and where the problem lies.
>
> Cheers,
> Peter
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-26 8:51 ` Burton, Ross
2013-09-26 9:19 ` Duan Fugang-B38611
2013-09-26 9:25 ` Duan Fugang-B38611
@ 2013-09-27 1:57 ` Duan Fugang-B38611
2 siblings, 0 replies; 24+ messages in thread
From: Duan Fugang-B38611 @ 2013-09-27 1:57 UTC (permalink / raw)
To: Duan Fugang-B38611, Burton, Ross
Cc: meta-freescale@yoctoproject.org, peter.hutterer@who-t.net,
Rutledge Shawn
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@who-t.net; Rutledge Shawn; meta-
> freescale@yoctoproject.org
> Subject: RE: Yacto rootfs: multi-touch message cannot handled by
> "close" button
>
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Data: Thursday, September 26, 2013 4:51 PM
>
> > To: Duan Fugang-B38611
> > Cc: peter.hutterer@who-t.net; Rutledge Shawn; meta-
> > freescale@yoctoproject.org
> > Subject: Re: Yacto rootfs: multi-touch message cannot handled by
> > "close" button
> >
> > On 26 September 2013 09:46, Duan Fugang-B38611 <B38611@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
^ permalink raw reply [flat|nested] 24+ messages in thread
* Yacto rootfs: multi-touch message cannot handled by "close" button
@ 2013-09-13 8:03 Duan Fugang-B38611
0 siblings, 0 replies; 24+ messages in thread
From: Duan Fugang-B38611 @ 2013-09-13 8:03 UTC (permalink / raw)
To: poky@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
Hi, all,
We use the X.Org X Server 1.14.0 + QT4.8.5 to do one demo, but I catch one issue: multi-touch message is not handled by "close" button.
I use egalax touchscreen for the multi-touch test.
After kernel up, evtest test the multi-touch message, all pass. Use xinput to do the test, also pass.
Open one QT app, all multi-touch message can be processed, but the window of the app cannot be closed by click the "X" button in the right-up region.
I test GNOME destop with the same kernel, any apps' window can be closed.
So, It is strange, maybe it is KDE issue for multi-touch ?
Current KDE is matchbox-window-manager.
Current multi-touch support messages:
root@imx6qsabresd:/# mtdev-test /dev/input/event0
supported mt events:
ABS_MT_TOUCH_MAJOR
ABS_MT_WIDTH_MAJOR
ABS_MT_POSITION_X
ABS_MT_POSITION_Y
ABS_MT_TRACKING_ID
Any response is appreciative.
Thanks,
Andy
[-- Attachment #2: Type: text/html, Size: 6209 bytes --]
^ permalink raw reply [flat|nested] 24+ messages in thread* Yacto rootfs: multi-touch message cannot handled by "close" button
@ 2013-09-13 8:03 Duan Fugang-B38611
0 siblings, 0 replies; 24+ messages in thread
From: Duan Fugang-B38611 @ 2013-09-13 8:03 UTC (permalink / raw)
To: yocto@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
Hi, all,
We use the X.Org X Server 1.14.0 + QT4.8.5 to do one demo, but I catch one issue: multi-touch message is not handled by "close" button.
I use egalax touchscreen for the multi-touch test.
After kernel up, evtest test the multi-touch message, all pass. Use xinput to do the test, also pass.
Open one QT app, all multi-touch message can be processed, but the window of the app cannot be closed by click the "X" button in the right-up region.
I test GNOME destop with the same kernel, any apps' window can be closed.
So, It is strange, maybe it is KDE issue for multi-touch ?
Current KDE is matchbox-window-manager.
Current multi-touch support messages:
root@imx6qsabresd:/# mtdev-test /dev/input/event0
supported mt events:
ABS_MT_TOUCH_MAJOR
ABS_MT_WIDTH_MAJOR
ABS_MT_POSITION_X
ABS_MT_POSITION_Y
ABS_MT_TRACKING_ID
Any response is appreciative.
Thanks,
Andy
[-- Attachment #2: Type: text/html, Size: 6106 bytes --]
^ permalink raw reply [flat|nested] 24+ messages in thread* Yacto rootfs: multi-touch message cannot handled by "close" button
@ 2013-09-13 8:02 Duan Fugang-B38611
2013-09-14 14:12 ` Daiane Angolini
0 siblings, 1 reply; 24+ messages in thread
From: Duan Fugang-B38611 @ 2013-09-13 8:02 UTC (permalink / raw)
To: meta-freescale@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
Hi, all,
We use the X.Org X Server 1.14.0 + QT4.8.5 to do one demo, but I catch one issue: multi-touch message is not handled by "close" button.
I use egalax touchscreen for the multi-touch test.
After kernel up, evtest test the multi-touch message, all pass. Use xinput to do the test, also pass.
Open one QT app, all multi-touch message can be processed, but the window of the app cannot be closed by click the "X" button in the right-up region.
I test GNOME destop with the same kernel, any apps' window can be closed.
So, It is strange, maybe it is KDE issue for multi-touch ?
Current KDE is matchbox-window-manager.
Current multi-touch support messages:
root@imx6qsabresd:/# mtdev-test /dev/input/event0
supported mt events:
ABS_MT_TOUCH_MAJOR
ABS_MT_WIDTH_MAJOR
ABS_MT_POSITION_X
ABS_MT_POSITION_Y
ABS_MT_TRACKING_ID
Any response is appreciative.
Thanks,
Andy
[-- Attachment #2: Type: text/html, Size: 6003 bytes --]
^ permalink raw reply [flat|nested] 24+ messages in thread* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-13 8:02 Duan Fugang-B38611
@ 2013-09-14 14:12 ` Daiane Angolini
2013-09-16 4:31 ` Duan Fugang-B38611
0 siblings, 1 reply; 24+ messages in thread
From: Daiane Angolini @ 2013-09-14 14:12 UTC (permalink / raw)
To: Duan Fugang-B38611; +Cc: meta-freescale@yoctoproject.org
On Fri, Sep 13, 2013 at 5:02 AM, Duan Fugang-B38611
<B38611@freescale.com> wrote:
> Hi, all,
>
>
>
> We use the X.Org X Server 1.14.0 + QT4.8.5 to do one demo, but I catch one
> issue: multi-touch message is not handled by “close” button.
>
>
>
> I use egalax touchscreen for the multi-touch test.
>
> After kernel up, evtest test the multi-touch message, all pass. Use xinput
> to do the test, also pass.
>
>
>
> Open one QT app, all multi-touch message can be processed, but the window of
> the app cannot be closed by click the “X” button in the right-up region.
>
> I test GNOME destop with the same kernel, any apps’ window can be closed.
>
>
>
> So, It is strange, maybe it is KDE issue for multi-touch ?
In fact, I have no idea if SATO can or cannot handle multi-touch, but, some time
ago, when I was testing touchscreen, the main problem I was not able to 'close'
anything was that my calibration was not right.
I mean, at the center of the screen the calibration was OK, but going
to the edges
of screen, the offset between my finger and pointer becomes bigger and bigger.
Could you, please, double check if your calibration is OK?
Daiane
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-14 14:12 ` Daiane Angolini
@ 2013-09-16 4:31 ` Duan Fugang-B38611
2013-09-16 11:25 ` Daiane Angolini
2013-09-16 16:31 ` Otavio Salvador
0 siblings, 2 replies; 24+ messages in thread
From: Duan Fugang-B38611 @ 2013-09-16 4:31 UTC (permalink / raw)
To: Daiane Angolini; +Cc: meta-freescale@yoctoproject.org
From: Daiane Angolini [mailto:daiane.list@gmail.com]
Data: Saturday, September 14, 2013 10:12 PM
> To: Duan Fugang-B38611
> Cc: meta-freescale@yoctoproject.org
> Subject: Re: [meta-freescale] Yacto rootfs: multi-touch message cannot
> handled by "close" button
>
> On Fri, Sep 13, 2013 at 5:02 AM, Duan Fugang-B38611 <B38611@freescale.com>
> wrote:
> > Hi, all,
> >
> >
> >
> > We use the X.Org X Server 1.14.0 + QT4.8.5 to do one demo, but I
> > catch one
> > issue: multi-touch message is not handled by "close" button.
> >
> >
> >
> > I use egalax touchscreen for the multi-touch test.
> >
> > After kernel up, evtest test the multi-touch message, all pass. Use
> > xinput to do the test, also pass.
> >
> >
> >
> > Open one QT app, all multi-touch message can be processed, but the
> > window of the app cannot be closed by click the "X" button in the right-
> up region.
> >
> > I test GNOME destop with the same kernel, any apps' window can be
> closed.
> >
> >
> >
> > So, It is strange, maybe it is KDE issue for multi-touch ?
>
> In fact, I have no idea if SATO can or cannot handle multi-touch, but,
> some time ago, when I was testing touchscreen, the main problem I was not
> able to 'close'
> anything was that my calibration was not right.
>
> I mean, at the center of the screen the calibration was OK, but going to
> the edges of screen, the offset between my finger and pointer becomes
> bigger and bigger.
>
> Could you, please, double check if your calibration is OK?
Daiane, thanks for your response.
I make sure the calibration is ok because I re-calibrate it using xinput_calibretor tool.
When I do the touch test I run the "xinput test XX" on the background, the print coordinate match the point that of I touch.
When I open the sub-windows of QT app, there have "cancel" button on the right-bottom , "X" icon on the right-up region.
I can close the sub-windows by click the "cancel" button, but fail by click the "X" icon of the sub-windows.
The sub-window region only cover at the center of the screen.
So, do you test the yacto touchscreen by multi-touch message ?
Thanks,
Andy
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-16 4:31 ` Duan Fugang-B38611
@ 2013-09-16 11:25 ` Daiane Angolini
2013-09-17 3:23 ` Duan Fugang-B38611
2013-09-16 16:31 ` Otavio Salvador
1 sibling, 1 reply; 24+ messages in thread
From: Daiane Angolini @ 2013-09-16 11:25 UTC (permalink / raw)
To: Duan Fugang-B38611; +Cc: meta-freescale@yoctoproject.org
On 09/16/2013 01:31 AM, Duan Fugang-B38611 wrote:
> From: Daiane Angolini [mailto:daiane.list@gmail.com]
> Data: Saturday, September 14, 2013 10:12 PM
>
>> To: Duan Fugang-B38611
>> Cc: meta-freescale@yoctoproject.org
>> Subject: Re: [meta-freescale] Yacto rootfs: multi-touch message cannot
>> handled by "close" button
>>
>> On Fri, Sep 13, 2013 at 5:02 AM, Duan Fugang-B38611 <B38611@freescale.com>
>> wrote:
>>> Hi, all,
>>>
>>>
>>>
>>> We use the X.Org X Server 1.14.0 + QT4.8.5 to do one demo, but I
>>> catch one
>>> issue: multi-touch message is not handled by "close" button.
>>>
>>>
>>>
>>> I use egalax touchscreen for the multi-touch test.
>>>
>>> After kernel up, evtest test the multi-touch message, all pass. Use
>>> xinput to do the test, also pass.
>>>
>>>
>>>
>>> Open one QT app, all multi-touch message can be processed, but the
>>> window of the app cannot be closed by click the "X" button in the right-
>> up region.
>>>
>>> I test GNOME destop with the same kernel, any apps' window can be
>> closed.
>>>
>>>
>>>
>>> So, It is strange, maybe it is KDE issue for multi-touch ?
>>
>> In fact, I have no idea if SATO can or cannot handle multi-touch, but,
>> some time ago, when I was testing touchscreen, the main problem I was not
>> able to 'close'
>> anything was that my calibration was not right.
>>
>> I mean, at the center of the screen the calibration was OK, but going to
>> the edges of screen, the offset between my finger and pointer becomes
>> bigger and bigger.
>>
>> Could you, please, double check if your calibration is OK?
>
> Daiane, thanks for your response.
>
> I make sure the calibration is ok because I re-calibrate it using xinput_calibretor tool.
> When I do the touch test I run the "xinput test XX" on the background, the print coordinate match the point that of I touch.
>
> When I open the sub-windows of QT app, there have "cancel" button on the right-bottom , "X" icon on the right-up region.
> I can close the sub-windows by click the "cancel" button, but fail by click the "X" icon of the sub-windows.
> The sub-window region only cover at the center of the screen.
>
> So, do you test the yacto touchscreen by multi-touch message ?
No, I have never tested multi-touch
>
> Thanks,
> Andy
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>
--
Daiane
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-16 11:25 ` Daiane Angolini
@ 2013-09-17 3:23 ` Duan Fugang-B38611
0 siblings, 0 replies; 24+ messages in thread
From: Duan Fugang-B38611 @ 2013-09-17 3:23 UTC (permalink / raw)
To: Angolini Daiane-B19406; +Cc: meta-freescale@yoctoproject.org
From: Angolini Daiane-B19406
Sent: Monday, September 16, 2013 7:26 PM
> To: Duan Fugang-B38611
> Cc: Daiane Angolini; meta-freescale@yoctoproject.org
> Subject: Re: [meta-freescale] Yacto rootfs: multi-touch message cannot
> handled by "close" button
>
> On 09/16/2013 01:31 AM, Duan Fugang-B38611 wrote:
> > From: Daiane Angolini [mailto:daiane.list@gmail.com]
> > Data: Saturday, September 14, 2013 10:12 PM
> >
> >> To: Duan Fugang-B38611
> >> Cc: meta-freescale@yoctoproject.org
> >> Subject: Re: [meta-freescale] Yacto rootfs: multi-touch message
> >> cannot handled by "close" button
> >>
> >> On Fri, Sep 13, 2013 at 5:02 AM, Duan Fugang-B38611
> >> <B38611@freescale.com>
> >> wrote:
> >>> Hi, all,
> >>>
> >>>
> >>>
> >>> We use the X.Org X Server 1.14.0 + QT4.8.5 to do one demo, but I
> >>> catch one
> >>> issue: multi-touch message is not handled by "close" button.
> >>>
> >>>
> >>>
> >>> I use egalax touchscreen for the multi-touch test.
> >>>
> >>> After kernel up, evtest test the multi-touch message, all pass. Use
> >>> xinput to do the test, also pass.
> >>>
> >>>
> >>>
> >>> Open one QT app, all multi-touch message can be processed, but the
> >>> window of the app cannot be closed by click the "X" button in the
> >>> right-
> >> up region.
> >>>
> >>> I test GNOME destop with the same kernel, any apps' window can be
> >> closed.
> >>>
> >>>
> >>>
> >>> So, It is strange, maybe it is KDE issue for multi-touch ?
> >>
> >> In fact, I have no idea if SATO can or cannot handle multi-touch,
> >> but, some time ago, when I was testing touchscreen, the main problem
> >> I was not able to 'close'
> >> anything was that my calibration was not right.
> >>
> >> I mean, at the center of the screen the calibration was OK, but going
> >> to the edges of screen, the offset between my finger and pointer
> >> becomes bigger and bigger.
> >>
> >> Could you, please, double check if your calibration is OK?
> >
> > Daiane, thanks for your response.
> >
> > I make sure the calibration is ok because I re-calibrate it using
> xinput_calibretor tool.
> > When I do the touch test I run the "xinput test XX" on the background,
> the print coordinate match the point that of I touch.
> >
> > When I open the sub-windows of QT app, there have "cancel" button on
> the right-bottom , "X" icon on the right-up region.
> > I can close the sub-windows by click the "cancel" button, but fail by
> click the "X" icon of the sub-windows.
> > The sub-window region only cover at the center of the screen.
> >
> > So, do you test the yacto touchscreen by multi-touch message ?
>
> No, I have never tested multi-touch
Daiane, thanks for your response.
Yacto treat as freescale imx6 release filesystem. The multi-touch issue may block the release.
Can you help to check the issue since you are familiar with yacto system.
Thanks,
Andy
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-16 4:31 ` Duan Fugang-B38611
2013-09-16 11:25 ` Daiane Angolini
@ 2013-09-16 16:31 ` Otavio Salvador
2013-09-17 1:46 ` Duan Fugang-B38611
1 sibling, 1 reply; 24+ messages in thread
From: Otavio Salvador @ 2013-09-16 16:31 UTC (permalink / raw)
To: Duan Fugang-B38611, Burton, Ross; +Cc: meta-freescale@yoctoproject.org
On Mon, Sep 16, 2013 at 1:31 AM, Duan Fugang-B38611
<B38611@freescale.com> wrote:
> I make sure the calibration is ok because I re-calibrate it using xinput_calibretor tool.
> When I do the touch test I run the "xinput test XX" on the background, the print coordinate match the point that of I touch.
>
> When I open the sub-windows of QT app, there have "cancel" button on the right-bottom , "X" icon on the right-up region.
> I can close the sub-windows by click the "cancel" button, but fail by click the "X" icon of the sub-windows.
> The sub-window region only cover at the center of the screen.
>
> So, do you test the yacto touchscreen by multi-touch message ?
So it may not be a Qt issue but a matchbox issue.
Ross, as the Matchbox maintainer, did you see anything like this
related to multitouch?
Regards,
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-16 16:31 ` Otavio Salvador
@ 2013-09-17 1:46 ` Duan Fugang-B38611
2013-09-17 9:41 ` Burton, Ross
0 siblings, 1 reply; 24+ messages in thread
From: Duan Fugang-B38611 @ 2013-09-17 1:46 UTC (permalink / raw)
To: Otavio Salvador, Burton, Ross; +Cc: meta-freescale@yoctoproject.org
From: Otavio Salvador <otavio@ossystems.com.br>
Sent: Tuesday, September 17, 2013 12:32 AM
> To: Duan Fugang-B38611; Burton, Ross
> Cc: Daiane Angolini; meta-freescale@yoctoproject.org
> Subject: Re: [meta-freescale] Yacto rootfs: multi-touch message cannot
> handled by "close" button
>
> On Mon, Sep 16, 2013 at 1:31 AM, Duan Fugang-B38611 <B38611@freescale.com>
> wrote:
> > I make sure the calibration is ok because I re-calibrate it using
> xinput_calibretor tool.
> > When I do the touch test I run the "xinput test XX" on the background,
> the print coordinate match the point that of I touch.
> >
> > When I open the sub-windows of QT app, there have "cancel" button on
> the right-bottom , "X" icon on the right-up region.
> > I can close the sub-windows by click the "cancel" button, but fail by
> click the "X" icon of the sub-windows.
> > The sub-window region only cover at the center of the screen.
> >
> > So, do you test the yacto touchscreen by multi-touch message ?
>
> So it may not be a Qt issue but a matchbox issue.
>
> Ross, as the Matchbox maintainer, did you see anything like this related
> to multitouch?
>
> Regards,
Thanks, Otavio.
Matchbox could enable touch if possible and then handle touch events which occur over that button, but if they instead enable touch and then only expect mouse events on their buttons, maybe that only works with some drivers and not others, or with some versions of XInput but not others.
I am not familiar with matchbox, maybe matchbox issue, maybe matchbox is configurable.
Ross, do you have any suggestion ? I have been blocked at the issue for many days.
Thanks,
Andy
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: Yacto rootfs: multi-touch message cannot handled by "close" button
2013-09-17 1:46 ` Duan Fugang-B38611
@ 2013-09-17 9:41 ` Burton, Ross
0 siblings, 0 replies; 24+ messages in thread
From: Burton, Ross @ 2013-09-17 9:41 UTC (permalink / raw)
To: Duan Fugang-B38611; +Cc: meta-freescale@yoctoproject.org, Otavio Salvador
On 17 September 2013 02:46, Duan Fugang-B38611 <B38611@freescale.com> wrote:
> Matchbox could enable touch if possible and then handle touch events which occur over that button, but if they instead enable touch and then only expect mouse events on their buttons, maybe that only works with some drivers and not others, or with some versions of XInput but not others.
>
> I am not familiar with matchbox, maybe matchbox issue, maybe matchbox is configurable.
>
> Ross, do you have any suggestion ? I have been blocked at the issue for many days.
Matchbox doesn't have any Xinput support, so it will be using the core
input events instead. You can use xev to verify that the core events
are being sent correctly.
Ross
^ permalink raw reply [flat|nested] 24+ messages in thread
end of thread, other threads:[~2013-09-30 2:34 UTC | newest]
Thread overview: 24+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-09-26 8:21 Yacto rootfs: multi-touch message cannot handled by "close" button Duan Fugang-B38611
2013-09-26 8:25 ` Burton, Ross
2013-09-26 8:46 ` Duan Fugang-B38611
2013-09-26 8:51 ` Burton, Ross
2013-09-26 9:19 ` Duan Fugang-B38611
2013-09-26 9:25 ` Duan Fugang-B38611
2013-09-26 9:45 ` Eric Bénard
2013-09-26 13:24 ` Duan Fugang-B38611
2013-09-26 13:31 ` Eric Bénard
2013-09-26 13:33 ` Duan Fugang-B38611
2013-09-26 15:57 ` Eric Bénard
2013-09-30 1:14 ` Peter Hutterer
2013-09-30 2:33 ` Duan Fugang-B38611
2013-09-27 1:57 ` Duan Fugang-B38611
-- strict thread matches above, loose matches on Subject: below --
2013-09-13 8:03 Duan Fugang-B38611
2013-09-13 8:03 Duan Fugang-B38611
2013-09-13 8:02 Duan Fugang-B38611
2013-09-14 14:12 ` Daiane Angolini
2013-09-16 4:31 ` Duan Fugang-B38611
2013-09-16 11:25 ` Daiane Angolini
2013-09-17 3:23 ` Duan Fugang-B38611
2013-09-16 16:31 ` Otavio Salvador
2013-09-17 1:46 ` Duan Fugang-B38611
2013-09-17 9:41 ` Burton, Ross
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.