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

Thu Sep 26 01:21:50 PDT 2013

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 at 01CEBAD3.5A59E670]

Thanks,
Andy

From: Peter Hutterer [mailto:peter.hutterer at 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 at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20130926/bcbe20a7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 159385 bytes
Desc: image001.png
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20130926/bcbe20a7/attachment.png>