Re: [meta-freescale] Yacto rootfs: multi-touch message cannot handled by close button
On Thu, Sep 26, 2013 at 01:24:59PM +, Duan Fugang-B38611 wrote: From: Eric Bénard [mailto:e...@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 +, Duan Fugang-B38611 b38...@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 + From: Duan Fugang-B38611 b38...@freescale.com To: Burton, Ross ross.bur...@intel.com CC: peter.hutte...@who-t.net peter.hutte...@who-t.net, Rutledge Shawn shawn.rutle...@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.bur...@intel.com] Data: Thursday, September 26, 2013 4:51 PM To: Duan Fugang-B38611 Cc: peter.hutte...@who-t.net; Rutledge Shawn; meta- freesc...@yoctoproject.org Subject: Re: Yacto rootfs: multi-touch message cannot handled by close button On 26 September 2013 09:46, Duan Fugang-B38611 b38...@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 0x101, 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 0x101, 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 0x101, 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 0x101, 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 0x101, 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 0x101, mode NotifyGrab, detail NotifyNonlinear VisibilityNotify event, serial 28, synthetic NO, window 0x101, 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 ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Yacto rootfs: multi-touch message cannot handled by close button
From: Peter Hutterer [mailto:peter.hutte...@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 +, Duan Fugang-B38611 wrote: From: Eric Bénard [mailto:e...@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 +, Duan Fugang-B38611 b38...@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 + From: Duan Fugang-B38611 b38...@freescale.com To: Burton, Ross ross.bur...@intel.com CC: peter.hutte...@who-t.net peter.hutte...@who-t.net, Rutledge Shawn shawn.rutle...@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.bur...@intel.com] Data: Thursday, September 26, 2013 4:51 PM To: Duan Fugang-B38611 Cc: peter.hutte...@who-t.net; Rutledge Shawn; meta- freesc...@yoctoproject.org Subject: Re: Yacto rootfs: multi-touch message cannot handled by close button On 26 September 2013 09:46, Duan Fugang-B38611 b38...@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 0x101, 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 0x101, 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 0x101, 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 0x101, 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 0x101, 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 0x101, mode NotifyGrab, detail NotifyNonlinear VisibilityNotify event, serial 28, synthetic NO, window 0x101, 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
Re: [meta-freescale] Yacto rootfs: multi-touch message cannot handled by close button
On 26 September 2013 09:21, Duan Fugang-B38611 b38...@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 ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Yacto rootfs: multi-touch message cannot handled by close button
On Sep 26, 2013 at 04:26pM, Ross ross.bur...@intel.commailto:ross.bur...@intel.com wrote: On 26 September 2013 09:21, Duan Fugang-B38611 b38...@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 ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Yacto rootfs: multi-touch message cannot handled by close button
On 26 September 2013 09:46, Duan Fugang-B38611 b38...@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 ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Yacto rootfs: multi-touch message cannot handled by close button
From: Burton, Ross [mailto:ross.bur...@intel.com] Data: Thursday, September 26, 2013 4:51 PM To: Duan Fugang-B38611 Cc: peter.hutte...@who-t.net; Rutledge Shawn; meta- freesc...@yoctoproject.org Subject: Re: Yacto rootfs: multi-touch message cannot handled by close button On 26 September 2013 09:46, Duan Fugang-B38611 b38...@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/210.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/210.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 ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Yacto rootfs: multi-touch message cannot handled by close button
Hi Duan, Le Thu, 26 Sep 2013 09:25:12 +, Duan Fugang-B38611 b38...@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 ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Yacto rootfs: multi-touch message cannot handled by close button
Le Thu, 26 Sep 2013 13:24:59 +, Duan Fugang-B38611 b38...@freescale.com a écrit : From: Eric Bénard [mailto:e...@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 +, Duan Fugang-B38611 b38...@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 ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Yacto rootfs: multi-touch message cannot handled by close button
From: Eric Bénard [mailto:e...@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 +, Duan Fugang-B38611 b38...@freescale.com a écrit : From: Eric Bénard [mailto:e...@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 +, Duan Fugang-B38611 b38...@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 ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Yacto rootfs: multi-touch message cannot handled by close button
Le Thu, 26 Sep 2013 13:33:41 +, Duan Fugang-B38611 b38...@freescale.com a écrit : Ok, do you have any thinking with the issue ? no idea, I'm not using X nor this display. Eric ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Yacto rootfs: multi-touch message cannot handled by close button
On 17 September 2013 02:46, Duan Fugang-B38611 b38...@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 ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
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.l...@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 b38...@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 ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
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 b38...@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.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] Yacto rootfs: multi-touch message cannot handled by close button
From: Daiane Angolini [mailto:daiane.l...@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 b38...@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 ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
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 b38...@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 ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
