> Thanks for the quick feedback, I think I need to look at the touch driver as well.
You're welcome. I think you won't need to do this anymore. Screens/kernel/drivers are probably fine.
I could eventually reproduce both issues in KWin and 1) was an Onboard thing. Wrong order of initialization, that apparently had no ill effect in compiz, where I did most of the touch testing. Trunk has a fix and I don't get the fall-back mouse-events mode anymore in KWin, meaning you'd likely have multi-touch available too. It works with either XInput or GTK event source here, but I'd suggest you return to "XInput", because a few of Onboard's features require/work better with this.
Still working on 2), though I expect you won't hit this anymore with default settings. Others might, wacom touch-screen people in particular (on KWin).
> AttributeError: 'X11DeviceXI2' object has no attribute 'touch_active'
Thank you, should be fixed too now.
> Thanks for the quick feedback, I think I need to look at the touch driver as well. kernel/ drivers are probably fine.
You're welcome. I think you won't need to do this anymore. Screens/
I could eventually reproduce both issues in KWin and 1) was an Onboard thing. Wrong order of initialization, that apparently had no ill effect in compiz, where I did most of the touch testing. Trunk has a fix and I don't get the fall-back mouse-events mode anymore in KWin, meaning you'd likely have multi-touch available too. It works with either XInput or GTK event source here, but I'd suggest you return to "XInput", because a few of Onboard's features require/work better with this.
Still working on 2), though I expect you won't hit this anymore with default settings. Others might, wacom touch-screen people in particular (on KWin).
> AttributeError: 'X11DeviceXI2' object has no attribute 'touch_active'
Thank you, should be fixed too now.