[Ubuntu-x-swat] [Bug 1084938] Re: evdev settings doesn't work at all
There isn't one. Trying to use a touchscreen to run regular desktop linux has major usability problems, as I'm sure you've noticed! My point is there is no mystery bug or hardware problem that's going to be solved by looking in logs. evdev's buttom emulation only works for touch pads, not touch screens. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1084938] Re: evdev settings doesn't work at all
There really isn't any mystery here. 3 button emulation only works for BUTTON events. This touchscreen generates TOUCH events. It's totally different kind of event than a mouse button getting clicked. 3 button emu doesn't exist for touch events. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1084938] Re: evdev settings doesn't work at all
Upon looking at the code in evdev, it's clear the third button emulation is completely non-functional for multitouch devices. The emulation is triggered by calling Evdev3BEmuFilterEvent() from EvdevPostQueuedEvents() in evdev.c. This is done for events of type EV_QUEUE_BTN only. With a multitouch touchscreen, events of this type aren't generated. Instead, the events are EV_QUEUE_TOUCH, which will never trigger the 3BEmu code. These touch events don't work the same way as button events, so it's not a simple matter of passing them to Evdev3BEmuFilterEvent() too. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1084938] Re: evdev settings doesn't work at all
The problem with the coordinate transform matrix not working is solved by this patch: http://patchwork.freedesktop.org/patch/12471/ These touchscreens sometimes only send one axis if the other axis hasn't changed. The server would take the new untransformed X axis sent by the screen and the saved, *post-transform*, value of the Y axis, and then apply the transform to that. The patch fixes it to take the new X axis and a saved pre-tranform Y axis and transform that. I can also confirm that emulate third button appears to be totally non- functional with an atmel touchscreen. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1084938 Title: evdev settings doesn't work at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1084938/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
Found out something new. I compiled the git version of evdev, xf86 -input-evdev-2.7.0-20-g5af11b6, and when multitouch isn't enabled, the core state problem is gone. The autoconf script doesn't detect XI22 on Precise because the X.org version is too old, so MT isn't enabled by default. Once I modified configure.ac to turn MULTITOUCH back on, then the problem was back as well and state is locked to 0x100 after the touchscreen is used. I've also found that I get far more of the problems Cédric mentions when ginn is running. It seems like what happens is the touchscreen stops generating ButtonPress events, but it still does motion events and state is still locked at 0x100. So the effect is that one is moving the pointer around with the button held down, but never pushing the button. This usually seems like left-click has stopped working. But I imagine the state problem and the resulting "drags with no click" can explain in some strange behavior seen in certain apps. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1015183/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
I see this same behavior on a Samsung Slate 7, which has an Atmel maxtouch multitouch touchscreen. Running Precise, with xserver-xorg- input-evdev 1:2.7.0-0ubuntu1.2 and xserver-xorg-core 2:1.11.4-0ubuntu10.8. If I don't touch the touchscreen since the X server has started, xev reports the state of events as expected when using a mouse. 0x000 for the ButtonPress, 0x100 for motion with the button down and the ButtonRelease, then 0x000 after. However, after the touchscreen is touched once, the state becomes 0x100 for the first ButtonPress from the touchscreen and stays at 0x100 thereafter, even after the ButtonRelease. Keyboard keys, mouse clicks, mouse motion, etc. are all state 0x100 until the X server is restarted. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1015183/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
