Hi, On 4/15/24 9:58 PM, Dmitry Torokhov wrote: > On Mon, Apr 15, 2024 at 09:50:37PM +0200, Hans de Goede wrote: >> Hi, >> >> On 4/15/24 9:40 PM, Dmitry Torokhov wrote: >>> 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. >> >> KEY_CONFIG is already generated by Fn + F# on some ThinkPads to launch >> the GNOME/KDE control center/panel and I believe that at least GNOME >> comes with a default binding to map KEY_CONFIG to the control-center. > > Not KEY_CONTROLPANEL? No when this was added most distros were still using X11 not Wayland so it was preferable to use KEY_foo symbols with codes below 240. > Are there devices that use both Fn+# and the doubleclick? Would it be an > acceptable behavior for the users to have them behave the same? That is a good question, at least my current ThinkPad does not have the Fn + F## combo for the control center anymore. So I guess we could indeed re-use KEY_CONFIG for the double-tap. Regards, Hans
