From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: XInput 2 support
Date: Sat, 16 Oct 2021 09:25:01 +0300 [thread overview]
Message-ID: <83ilxxij0i.fsf@gnu.org> (raw)
In-Reply-To: <87r1clh6nq.fsf@yahoo.com> (message from Po Lu on Sat, 16 Oct 2021 13:37:13 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Date: Sat, 16 Oct 2021 13:37:13 +0800
>
> I hacked up support for handling XInput 2 events, though it hasn't
> undergone any serious testing yet.
Thanks. Would people who have this installed try the patch and report
what they see?
> So the only advantage of this code over the existing Core Input code as
> of present would be not relying on a fragile environment variable
> (GDK_CORE_DEVICE_EVENTS) to work properly in GTK 3 builds. Call me
> paranoid, but this variable reeks of something that the GTK developers
> will remove at some point in the future. (AFAIK, it's already been
> removed in GTK 4).
Who or what will promise us that XInput 2 will not be removed by those
same developers?
> However, it paves the way for future support of high-resolution
> scrollwheels, multi-touch trackpad support, and much more.
>
> Would this support be worth installing? Thanks.
Much of the code seems to be just a copy of the existing code in
xterm.c, just with different events. Would it be possible to
preprocess XInput 2 events into X events, and then call the existing
code, instead of copy/paste-ing it?
Also, do these changes have any effect on user-visible behavior, or on
how users must set up their systems or how they use Emacs? If so,
there should be suitable changes to the documentation.
next prev parent reply other threads:[~2021-10-16 6:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r1clh6nq.fsf.ref@yahoo.com>
2021-10-16 5:37 ` XInput 2 support Po Lu
2021-10-16 6:25 ` Eli Zaretskii [this message]
2021-10-16 6:29 ` Po Lu
2021-10-16 6:45 ` Po Lu
2021-10-16 7:45 ` Po Lu
2021-10-16 11:38 ` Po Lu
2021-10-17 10:09 ` Alan Third
2021-10-17 12:10 ` Po Lu via Emacs development discussions.
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=83ilxxij0i.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.