With that patch by Chase, I also wonder what would happen if two touch devices were used simultaneously.
When I both touch my screen and click my conventional mouse button, I get two button events, but the state is the bitwise or of both, so the second click will be "pressed button 1 while button 1 was pressed". Makes sense, in a certain way, although it might well confuse some applications.
But what if I had two touch devices controlling the core pointer? I believe it is likely with the current setup that in this case, the second device would generate a ButtonPress with state 0x000. Or is it impossible for more than one touch device to control the core pointer at a given time? I don't have more than one device, so I can't test this.
I'll agree that given current technology, this seems a rather rare corner case, and probably not worth the effort to deal with properly. But any shortcomings in that respect should perhaps at least be documented somewhere.
With that patch by Chase, I also wonder what would happen if two touch devices were used simultaneously.
When I both touch my screen and click my conventional mouse button, I get two button events, but the state is the bitwise or of both, so the second click will be "pressed button 1 while button 1 was pressed". Makes sense, in a certain way, although it might well confuse some applications.
But what if I had two touch devices controlling the core pointer? I believe it is likely with the current setup that in this case, the second device would generate a ButtonPress with state 0x000. Or is it impossible for more than one touch device to control the core pointer at a given time? I don't have more than one device, so I can't test this.
I'll agree that given current technology, this seems a rather rare corner case, and probably not worth the effort to deal with properly. But any shortcomings in that respect should perhaps at least be documented somewhere.