On Mon, Feb 07, 2011 at 12:16:20PM -0500, Chase Douglas wrote:
On 02/07/2011 11:00 AM, Henrik Rydberg wrote:
This is a function of the fact that you can do two very
different things
with your finger: move the pointer, or interact with content/
gesture. I
think we could special case that in pointer-based environments
like the
desktop, so that single-finger pointer moving actions come to an
end
when additional fingers are brought to bear, at which point a
gesture is
begun. Would that address the issue?
The devil is in the details here. The worry is that we can find
ourselves in inconsistent states and/or complicate the
implementation to
the point that it's unworkable or prohibits other use cases.
I don't think we need to over-dramatize this particular case.
Rather,
acknowledging that a hovering pen, a finger on a trackpad, and a
hovering finger on a screen all constitute a real situation not
properly accounted for, should make it possible to resolve this
issue
cleanly.
I agree that xi 2.1 doesn't handle this cleanly. The major reason for
this is the interaction between touch and cursors, and gestures and
X.
We are trying to fit touch into a system that is poorly designed
for it,
and we are trying to fit gestures either before the X input stack or
after it. No implementation is going to be perfect given these
constraints.
We can strive for a better system in wayland, but some compromises
must
be made for X.
Again, I think we need to turn the logic upside down. What do we need
to achieve what we want, and do it that way.
