From: Eli Zaretskii <eliz@gnu.org>
To: rudalics@gmx.at, juri@linkov.net
Cc: adam@alphapapa.net, emacs-devel@gnu.org
Subject: Re: tab-bar: Defining another mouse-button binding?
Date: Sat, 11 Sep 2021 14:03:20 +0300 [thread overview]
Message-ID: <83r1dvgyrr.fsf@gnu.org> (raw)
In-Reply-To: <83sfybh2n2.fsf@gnu.org> (message from Eli Zaretskii on Sat, 11 Sep 2021 12:39:45 +0300)
> Date: Sat, 11 Sep 2021 12:39:45 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: adam@alphapapa.net, emacs-devel@gnu.org, juri@linkov.net
>
> > With mouse wheel scrolls one has to be always prepared that the scroll
> > is intended for one window while the mouse is positioned anywhere on
> > your frame.
>
> That's not the problem here, AFAICT. The problem here, at least for
> GUI frames, is that the code Juri wrote supports only mice that report
> wheel events as button events. That code doesn't support mice which
> report true mouse-wheel events (so I guess NS is also affected?). I'm
> working on a fix.
>
> I didn't yet look at the TTY frame case.
OK, I think I fixed this: tab-bar scrolling should now work for mice
which report mouse-wheel events.
I recalled the problem with supporting that on MS-Windows consoles:
the coordinates reported by console APIs for the mouse-scroll events
is relative to the top-level corner of the display screen, not that of
the console window (see the comment in w32inevt.c). This, of course,
make the coordinates inappropriate for detecting scrolling of the tab
bar and tab line on MS-Windows consoles, so they don't work there. If
someone knows how to fix this, I'm all ears.
prev parent reply other threads:[~2021-09-11 11:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 9:37 tab-bar: Defining another mouse-button binding? Adam Porter
2021-09-08 18:12 ` Juri Linkov
2021-09-08 19:00 ` Adam Porter
2021-09-08 19:23 ` Juri Linkov
2021-09-09 7:53 ` Juri Linkov
2021-09-09 17:28 ` Eli Zaretskii
2021-09-09 18:58 ` Juri Linkov
2021-09-09 19:15 ` Eli Zaretskii
2021-09-09 19:19 ` Juri Linkov
2021-09-09 19:38 ` Eli Zaretskii
2021-09-10 6:36 ` Juri Linkov
2021-09-10 7:05 ` Eli Zaretskii
2021-09-10 16:19 ` Juri Linkov
2021-09-10 17:59 ` Eli Zaretskii
2021-09-11 8:39 ` martin rudalics
2021-09-11 9:39 ` Eli Zaretskii
2021-09-11 11:03 ` Eli Zaretskii [this message]
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=83r1dvgyrr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=adam@alphapapa.net \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=rudalics@gmx.at \
/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).