[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zh2CtKy1NfKfojzS@google.com>
Date: Mon, 15 Apr 2024 12:40:36 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Mark Pearson <mpearson-lenovo@...ebb.ca>
Cc: Peter Hutterer <peter.hutterer@...hat.com>,
Hans de Goede <hdegoede@...hat.com>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
Henrique de Moraes Holschuh <hmh@....eng.br>,
ibm-acpi-devel@...ts.sourceforge.net,
"platform-driver-x86@...r.kernel.org" <platform-driver-x86@...r.kernel.org>,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
Nitin Joshi1 <njoshi1@...ovo.com>,
Vishnu Sankar <vsankar@...ovo.com>
Subject: Re: [PATCH 1/4] Input: Add trackpoint doubletap and system debug
info keycodes
On Wed, Apr 10, 2024 at 10:48:10PM -0400, Mark Pearson wrote:
>
> I have a stronger preference to keep the KEY_DOUBLECLICK - that one seems less controversial as a genuine new input event.
Please see my response to Peter's letter. I think it very much depends
on how it will be used (associated with the pointer or standalone as it
is now).
For standalone application, recalling your statement that on Win you
have this gesture invoke configuration utility I would argue for
KEY_CONFIG for it.
Thanks.
--
Dmitry
Powered by blists - more mailing lists