Looks double click not wrorking is caused by X.org driver, :-(
On Mon, Apr 23, 2012 at 11:34 PM, Benjamin Tissoires <email address hidden> wrote:
> You can understand my email as a regression report for the Quanta touchscreen
> device, since it works well on 3.0 kernel, but double click stops working
> on 3.4-rc2.
Well, depending on the point of view, it's a regression or a feature ;-)
in kernels pre-3.2 IIRC, this device used the embedded mouse interface
(so the double click "worked"). Now, it's using the generic
hid-multitouch driver, which means that it forwards raw multitouch
events to the upper layers.
The problem relies in the upper layers and not in the kernel: nobody
took the time to code a X.org driver that handles true multitouch
direct devices. You can eventually use the synaptics one, but you will
have to deal with absolute/relative coordinates, and the last time I
played with it, it was not convenient as I was not able to make GDM
use the absolute coordinate system (I kow I should have patched the
synaptics X.org driver).
Looks double click not wrorking is caused by X.org driver, :-(
On Mon, Apr 23, 2012 at 11:34 PM, Benjamin Tissoires <email address hidden> wrote:
> You can understand my email as a regression report for the Quanta touchscreen
> device, since it works well on 3.0 kernel, but double click stops working
> on 3.4-rc2.
Well, depending on the point of view, it's a regression or a feature ;-)
in kernels pre-3.2 IIRC, this device used the embedded mouse interface
(so the double click "worked"). Now, it's using the generic
hid-multitouch driver, which means that it forwards raw multitouch
events to the upper layers.
The problem relies in the upper layers and not in the kernel: nobody
took the time to code a X.org driver that handles true multitouch
direct devices. You can eventually use the synaptics one, but you will
have to deal with absolute/relative coordinates, and the last time I
played with it, it was not convenient as I was not able to make GDM
use the absolute coordinate system (I kow I should have patched the
synaptics X.org driver).
see detailed discussion on
http:// www.spinics. net/lists/ linux-input/ msg20458. html