Missing support for GeneralTouch Win7 TwoFinger device
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Open Input Framework |
Fix Released
|
Wishlist
|
Chase Douglas |
Bug Description
This issue was originally reported by Vincent Gerris (MacRules) as part of bug #637106. We have moved it here, since it wasn't related to that particular ticket. Here are some comments from Vincent from that ticket which outline the issue:
Comment #6:
What happens is, that if I touch the screen, the cursor does not move from the previous position sometimes.
For example when I touch 6 different places on the screen, the cursor would follow 3 times and the other 3 not (it would remain at the 3rd position).
Things that effect this: when I press harder on the screen, sometimes the cursor does appear on that spot.
When I touch and then drag, the cursor always follows.
Please not that this does not happen on Ubuntu 10.04, so this is related to X/evdev.
Besides all this, I have PyMT om my device.
When that is configured to use the mtdev driver, the demo works fine for two fingers, meaning while X has trouble following, PyMT shows no trouble.
That would make me think it is not a driver issue, but that is just my point of view :).
The other thing is, when I use the driver that does not send the mtY and mtX (both) then this issue also does not occur.
So linking all that, I would think that when a touch is performed, some mechanism checks if both mtX and mtY are there and if so, tries to determine something about a simple touch that couses a different interpretaton to X then expected.
Comment #4:
My device is identified as a GeneralTouch Win7 TwoFinger device.
The hardware ID is 0dfc:0001 . I am using a driver developed by Stephane Chatty from enac.fr .
I am running Ubuntu 10.10 where I have this issue, but I have also a 10.04 install with the 2.3.35 kernel from 10.10 running with the same driver, and I do not have the issue there.
From bug #637106, Chase and I both think that Vincent's issue is driver related. That's a first guess, though. We can use this ticket as a basis for evaluation and requests for more information.
This first order of business is for MacRules to follow up on device calibration, and see if that makes any difference. He noted in the other bug that he's going to do this.