@Sebastian: I guess I didn't make myself clear. Typical usage is Stick+Pad are OR'd by the X in the "core" pointer. As you say. The point of the state machine (it's a s.m. only theoretically, it's very simple actually and there won't be any corner cases) is to *emulate* two independent mice when Stick & Pad are joined within "core" pointer. Emulate by simple button-event masking.
Stuck buttons issue is of course solved more easily by mere merging, as you did, but that way we really get just two pointers with one set of buttons. It's perfectly OK, because the ALPS behaves like this. It is our *obvious* way out. BUT - I don't like this behaviour. :) Most usage patterns wouldn't see any difference, but there are some patterns, which won't work with merged buttons. I'll describe it later, this is just a short reply to keep you updated and to *celebrate* another, the best so far, version based on our recent work and research. Yay! :) Merging (cloning buttons into both Inputs) doesn't allow actions like: wheel emulation using btn3 on Stick AND no wheel emulation using btn3 on Pad (or some action on Pad *different* from Stick). Independent mice would have no trouble in such setup. If we mask ALPS buttons, this will work. Even the most border-line/special usage patterns would work as if two independent mice were used. For me, it's enough pain having to use Pad that I'd rather fix it myself. I suggest you forget about it, I'll ask you to stress-test it when finished; check if it breaks something on your model, etc. OK? More important, as you say, is the 9p flag. I'll continue tomorrow - I spent all day today working on a new fence *outside*. Yep, one of _those_ experiences. :) -- ALPS DualPoint Touchpad flaky performance https://bugs.launchpad.net/bugs/296610 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
