> I noticed that myself and got some complaints like this. > https://github.com/hanipouspilot/ubuntu-fixes/issues/2 > > General issue is that when one finger is on the touchpad, movement of a > second finger is ignored, if the first finger does not move. > Usually with other touchpads, when you have one finger on the touchpad and > move the other, it is recognized as two-finger scrolling. > The device itself sends relative packages as normal in that case, but linux > driver ignores them, until first finger is moved. > > I guess, Windows driver behaves same way. I can't test it, since I do not > have Windows installed on that laptop. > > As I understood, Windows driver ignores that one finger is on button area and > recognizes movement of the other as one-finger movement. > > It is clear that we do not know the full protocol or parameters of all > touchpad models to have that button area always correct. > But it looks like button area is set when 3rd byte in abs package is 00. > There is a good chance that it is common for all touchpad models. > > Do you have ideas how to fix it the easiest way? > > Regards, > > Dmitry >
I looked at it some more and noticed that if I put one finger on touchpad, then another, then move the second one, rel packets are ignored. But if keeping both fingers on touchpad, I move the first one, rel packets work OK. This is wrong. I can't get what's wrong with the code at the moment. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
