From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: larsi@gnus.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Touchscreen support
Date: Sun, 19 Dec 2021 10:14:30 +0200 [thread overview]
Message-ID: <834k759fkp.fsf@gnu.org> (raw)
In-Reply-To: <877dc1cug5.fsf@yahoo.com> (message from Po Lu on Sun, 19 Dec 2021 08:24:58 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, monnier@iro.umontreal.ca,
> emacs-devel@gnu.org
> Date: Sun, 19 Dec 2021 08:24:58 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > FWIW, MS-Windows seems to provide higher-level abstraction for touch
> > events, see
> >
> > https://docs.microsoft.com/en-us/windows/win32/wintouch/windows-touch-gestures-overview
> >
> > Is the plan to have xterm.c/xfns.c to generate similar higher-level
> > events based on just the 3 basic low-level events we now have in
> > xterm.c?
>
> The plan is to have that infrastructure in Lisp, which should be much
> more portable (for example, judging by the MS documentation you sent,
> there are at least 3 gestures not supported by GTK: left/right selection
> drag, flicks, and I think rotate as well.)
If you do it in Lisp, it will be hard to use on other platforms, where
the higher-level abstractions are reported on the level of the
window-system events.
> MS-Windows does support the low level reporting of touch events like
> we have in xterm.c, correct?
I don't think so, although I'm far from being an expert. I see it
provides the gesture-begin and gesture-end events, but not
gesture-update; instead, the "cooked" gestures are provided which are
already constructed from lower-level events. The MS documentation
clearly says:
Note Most applications should ignore the GID_BEGIN and GID_END
messages and pass them to DefWindowProc. These messages are used by
the default gesture handler. Application behavior is undefined when
the GID_BEGIN and GID_END messages are consumed by a third-party
application.
So they advise against using the low-level events.
In any case, it makes no sense to me to "decompose" events that are
already composed into meaningful gestures. We should be able to use
those higher-level abstractions when they are provided.
next prev parent reply other threads:[~2021-12-19 8:14 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87czlxkntg.fsf.ref@yahoo.com>
2021-12-16 7:31 ` Touchscreen support Po Lu via Emacs development discussions.
2021-12-16 7:58 ` Lars Ingebrigtsen
2021-12-16 8:02 ` Po Lu
2021-12-17 6:19 ` Po Lu
2021-12-17 7:17 ` Lars Ingebrigtsen
2021-12-17 12:29 ` Stefan Monnier
2021-12-17 12:36 ` Po Lu
2021-12-17 13:18 ` Stefan Monnier
2021-12-17 13:48 ` Po Lu
2021-12-17 16:00 ` Stefan Monnier
2021-12-18 0:02 ` Po Lu
2021-12-18 16:22 ` Stefan Monnier
2021-12-18 19:12 ` Stefan Monnier
2021-12-18 4:41 ` Richard Stallman
2021-12-18 4:53 ` Po Lu
2021-12-20 4:42 ` Richard Stallman
2021-12-20 4:59 ` Po Lu
2021-12-21 4:15 ` Richard Stallman
2021-12-21 4:35 ` Po Lu
2021-12-22 4:16 ` Richard Stallman
2021-12-22 4:39 ` Po Lu
2021-12-23 3:43 ` Richard Stallman
2021-12-23 4:46 ` Po Lu
2021-12-26 3:57 ` Richard Stallman
2021-12-26 5:02 ` Po Lu
2021-12-27 4:14 ` Richard Stallman
2021-12-27 6:05 ` Stefan Monnier
2021-12-28 4:19 ` Richard Stallman
2022-01-15 0:17 ` chad
2022-01-15 0:48 ` Po Lu
2022-01-16 5:07 ` Richard Stallman
2022-01-16 5:35 ` Po Lu
2021-12-18 7:48 ` Lars Ingebrigtsen
2021-12-18 14:46 ` Eli Zaretskii
2021-12-19 0:24 ` Po Lu
2021-12-19 8:14 ` Eli Zaretskii [this message]
2021-12-19 9:24 ` Po Lu
2021-12-19 9:32 ` Eli Zaretskii
2021-12-19 9:38 ` Po Lu
2021-12-19 11:31 ` Eli Zaretskii
2021-12-19 11:42 ` Po Lu
2021-12-19 17:58 ` Eli Zaretskii
2021-12-20 0:54 ` Po Lu
2021-12-20 15:18 ` Eli Zaretskii
2021-12-21 1:08 ` Po Lu
2021-12-21 12:11 ` Eli Zaretskii
2021-12-21 12:21 ` Po Lu
2021-12-21 14:17 ` Eli Zaretskii
2021-12-19 18:26 ` [External] : " Drew Adams
2021-12-20 4:42 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834k759fkp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).