linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henrik Rydberg <rydberg@euromail.se>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Jiri Kosina <jkosina@suse.cz>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] input: mt: Interface and MT_TOOL documentation updates
Date: Tue, 14 Dec 2010 00:25:26 +0100	[thread overview]
Message-ID: <4D06AB66.8090909@euromail.se> (raw)
In-Reply-To: <4D06A60D.7010409@canonical.com>

>> The envelope contacts serve as a way to detect a small area of fingers or a

>> large area of fingers. There is nothing inherently problematic with having one
>> or three or more such contacts.
> 
> Then I'm more confused :).
> 
> I see one problem: devices that report two touch points, (X1, Y1) and
> (X2, Y2), but in reality the touches could be at (X1, Y2) and (X2, Y1)
> instead. Using a rectangle helps resolve this issue for panning and
> pinching, though not for rotation.


If panning and pinching and rotation could all be recovered properly, then the
individual contacts could actually have been reconstructed properly in the first
place. This is the whole point - there is not enough information available for
rotation to be recovered properly.

Thanks.
Henrik

  reply	other threads:[~2010-12-13 23:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-10 17:24 [PATCH v2] input: mt: Interface and MT_TOOL documentation updates Henrik Rydberg
2010-12-10 17:36 ` Dmitry Torokhov
2010-12-10 17:41   ` Henrik Rydberg
2010-12-10 17:42     ` Ping Cheng
2010-12-10 17:47       ` Henrik Rydberg
2010-12-14  3:53         ` Peter Hutterer
2010-12-13 17:46 ` Chase Douglas
2010-12-13 21:21   ` Henrik Rydberg
2010-12-13 23:02     ` Chase Douglas
2010-12-13 23:25       ` Henrik Rydberg [this message]
2010-12-14  4:36         ` Peter Hutterer
2010-12-14  9:10           ` Henrik Rydberg
2010-12-20  8:17             ` Peter Hutterer
2010-12-14 14:33           ` Chris Bagwell
2010-12-14 15:02       ` Chris Bagwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D06AB66.8090909@euromail.se \
    --to=rydberg@euromail.se \
    --cc=chase.douglas@canonical.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).