From: Chase Douglas <chase.douglas@canonical.com>
To: Benjamin Tissoires <benjamin.tissoires@enac.fr>
Cc: Ming Lei <tom.leiming@gmail.com>, Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org
Subject: Re: HID regression: Quanta touchscreen, device ID: 0408:3008
Date: Mon, 23 Apr 2012 08:59:07 -0700 [thread overview]
Message-ID: <4F957C4B.2020408@canonical.com> (raw)
In-Reply-To: <CAN+gG=HJVynUaLciTkKqMSvciU1RN9NssQOBGeH2Wkg=9b6kOQ@mail.gmail.com>
On 04/23/2012 08:48 AM, Benjamin Tissoires wrote:
> On Mon, Apr 23, 2012 at 17:42, Chase Douglas
> <chase.douglas@canonical.com> wrote:
>> On 04/23/2012 08:34 AM, Benjamin Tissoires wrote:
>>> The problem relies in the upper layers and not in the kernel: nobody
>>> took the time to code a X.org driver that handles true multitouch
>>> direct devices. You can eventually use the synaptics one, but you will
>>> have to deal with absolute/relative coordinates, and the last time I
>>> played with it, it was not convenient as I was not able to make GDM
>>> use the absolute coordinate system (I kow I should have patched the
>>> synaptics X.org driver).
>>
>> X now supports direct multitouch devices using the X evdev driver. This
>> may be a bug in the X server.
>
> Yes it does, but does it also emulates right-clicks with double tap?
> (It's not an attack ;-), it's just a question as I did not followed
> the development of XInput 2.2 since a long time...)
No offense taken :). I merely wanted to point out that it could be a bug
in the X server, too.
In XI 2.2, there is only button 1 emulation. If you double tap it should
double click. If you press and hold, it should press and hold button 1.
There's no "gestural" interpretation in the X server that interprets
touchscreen input and causes a button 2 event.
-- Chase
prev parent reply other threads:[~2012-04-23 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 7:26 HID regression: Quanta touchscreen, device ID: 0408:3008 Ming Lei
2012-04-23 13:43 ` Jiri Kosina
2012-04-23 14:19 ` Ming Lei
2012-04-23 14:26 ` Jiri Kosina
[not found] ` <4f95669e.a0e7d80a.2ef7.6710SMTPIN_ADDED@mx.google.com>
2012-04-23 15:34 ` Benjamin Tissoires
2012-04-23 15:42 ` Chase Douglas
2012-04-23 15:48 ` Benjamin Tissoires
2012-04-23 15:59 ` Chase Douglas [this message]
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=4F957C4B.2020408@canonical.com \
--to=chase.douglas@canonical.com \
--cc=benjamin.tissoires@enac.fr \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=tom.leiming@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.