From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: master e37eb7f: Add support for pixel wheel deltas on NS
Date: Sat, 27 Nov 2021 14:02:28 +0200 [thread overview]
Message-ID: <83h7bxzu0b.fsf@gnu.org> (raw)
In-Reply-To: <8735nhbz74.fsf@yahoo.com> (message from Po Lu on Sat, 27 Nov 2021 19:44:15 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Sat, 27 Nov 2021 19:44:15 +0800
>
> > if (CONSP (event->arg))
> > return list5 (head, position, make_fixnum (double_click_count),
> > XCAR (event->arg), Fcons (XCAR (XCDR (event->arg)),
> > XCAR (XCDR (XCDR (event->arg)))));
> >
> > ? If so, this always produces a 5-element list, and CLICKS is always
> > included. Right?
>
> Yes, but event->arg might not always be a cons. On X, it is only a cons
> in XInput 2 events that have precise scrolling information. When
> handling legacy events, it is nil.
I did mean what happens when the precise scrolling information is
there.
> AFAIU (and this may not be a very accurate understanding), if event->arg
> is a cons, it means it might have line scroll information, and has pixel
> scroll information.
>
> Otherwise, if it is a number, it has only line information.
>
> Otherwise, if the wheel event is double or triple, `double_click_count'
> will be included.
>
> And otherwise, only the event name and position will be included.
So I think the manual should describe these possibilities, i.e. that
every member past POSITION can be present or absent, and if it's
present, the next one could be present or absent, etc.
next prev parent reply other threads:[~2021-11-27 12:02 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211125030922.2353.1129@vcs0.savannah.gnu.org>
[not found] ` <20211125030924.7258E2094B@vcs0.savannah.gnu.org>
2021-11-25 10:26 ` master e37eb7f: Add support for pixel wheel deltas on NS Robert Pluim
2021-11-25 10:34 ` Po Lu
2021-11-25 10:47 ` Robert Pluim
2021-11-25 11:02 ` Eli Zaretskii
2021-11-26 0:39 ` Po Lu
2021-11-26 6:35 ` Eli Zaretskii
2021-11-26 7:00 ` Po Lu
2021-11-26 8:17 ` Eli Zaretskii
2021-11-26 9:37 ` Po Lu
2021-11-26 11:32 ` Eli Zaretskii
2021-11-26 11:44 ` Po Lu
2021-11-26 16:55 ` Eli Zaretskii
2021-11-27 0:02 ` Po Lu
2021-11-27 6:09 ` Eli Zaretskii
2021-11-27 6:41 ` Po Lu
2021-11-27 7:05 ` Eli Zaretskii
2021-11-27 7:14 ` Po Lu
2021-11-27 10:47 ` Eli Zaretskii
2021-11-27 10:54 ` Po Lu
2021-11-27 11:03 ` Eli Zaretskii
2021-11-27 11:05 ` Po Lu
2021-11-27 11:13 ` Po Lu
2021-11-27 11:32 ` Eli Zaretskii
2021-11-27 11:34 ` Po Lu
2021-11-27 11:40 ` Eli Zaretskii
2021-11-27 11:44 ` Po Lu
2021-11-27 12:02 ` Eli Zaretskii [this message]
2021-11-27 12:11 ` Po Lu
2021-11-27 12:36 ` Eli Zaretskii
2021-11-27 12:48 ` Po Lu
2021-11-26 11:48 ` Eli Zaretskii
2021-11-26 12:05 ` Po Lu
2021-11-26 12:23 ` Eli Zaretskii
2021-11-26 12:37 ` Po Lu
2021-11-26 19:39 ` Alan Third
2021-11-26 19:45 ` Eli Zaretskii
2021-11-26 19:54 ` Alan Third
2021-11-28 2:54 ` Po Lu
2021-11-28 7:53 ` Eli Zaretskii
2021-11-28 7:58 ` Po Lu
2021-11-28 8:28 ` Eli Zaretskii
2021-11-29 7:39 ` Po Lu
2021-11-29 12:50 ` Eli Zaretskii
2021-11-29 13:19 ` Po Lu
2021-11-25 11:00 ` Eli Zaretskii
2021-11-25 18:46 ` Stefan Monnier
2021-11-25 18:58 ` Eli Zaretskii
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=83h7bxzu0b.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 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).