From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: XInput 2 support
Date: Sat, 16 Oct 2021 14:29:52 +0800 [thread overview]
Message-ID: <87bl3ph47z.fsf@yahoo.com> (raw)
In-Reply-To: <83ilxxij0i.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 16 Oct 2021 09:25:01 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Who or what will promise us that XInput 2 will not be removed by those
> same developers?
XInput 2 is currently the standard modern input handling extension on
X-Windows, and GTK uses it to provide input features such as smooth
scrolling and touchscreen support on X-Windows whenever available. The
legacy Core Input code is not as well maintained, and is missing certain
features.
> 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?
I've already done that where possible (see the variables `ev' and `bv'
under "case GenericEvent:"). Everywhere else, I'm not comfortable with
preprocessing these XI events into X events.
> 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.
None at all. The code falls back to Core Input if the X Server does not
have XInput2 installed, and the behaviour is identical when using both.
Thanks.
next prev parent reply other threads:[~2021-10-16 6:29 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
2021-10-16 6:29 ` Po Lu [this message]
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=87bl3ph47z.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.
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.