@charles: Hello Charles, the latest patch I just submitted fixes this behaviour. I noticed it too, in a different way, but I think I know what you mean. The patch is still being worked on; the button merging algorithm which is responsible for the double clicking was the most straightforward way to go at the time. I even agreed with Sebastian. Personally, I needed some time for other stuff before I could implement the button masking I promised. It should solve all button issues AND make the HW-merged devices perform in almost every respect like two *independent* devices.
Try the latest patch I uploaded just now. I've been using it for over a day and haven't had a single issue. And like I mentioned, all TP+Stick tricks I learned on my old ThinkPad work now. They require independent mice, so they wouldn't work with previous versions at all.
The more testing the better.
PS: uploading binary for Ubuntu "linux-image-2.6.31-15-generic-pae" version 2.6.31-15.50.
@charles: Hello Charles, the latest patch I just submitted fixes this behaviour. I noticed it too, in a different way, but I think I know what you mean. The patch is still being worked on; the button merging algorithm which is responsible for the double clicking was the most straightforward way to go at the time. I even agreed with Sebastian. Personally, I needed some time for other stuff before I could implement the button masking I promised. It should solve all button issues AND make the HW-merged devices perform in almost every respect like two *independent* devices.
Try the latest patch I uploaded just now. I've been using it for over a day and haven't had a single issue. And like I mentioned, all TP+Stick tricks I learned on my old ThinkPad work now. They require independent mice, so they wouldn't work with previous versions at all.
The more testing the better.
PS: uploading binary for Ubuntu "linux- image-2. 6.31-15- generic- pae" version 2.6.31-15.50.