From: Manuel Giraud via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 62707@debbugs.gnu.org
Subject: bug#62707: 30.0.50; [PATCH] Non toolkit scroll bar handle
Date: Fri, 07 Apr 2023 09:55:21 +0200 [thread overview]
Message-ID: <87pm8gdt3q.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <83cz4gp3ps.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 07 Apr 2023 10:10:39 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Fri, 07 Apr 2023 08:46:14 +0200
>> From: Manuel Giraud via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> I'd like to fix how the handle of scroll bars in non-toolkit build keeps
>> changing size when scrolling a file.
>
> Fix it in what way? what is wrong with what we have now?
When I'm scrolling a file (with 'C-v'/'M-v' for example), the handle of
the vertical scroll bar has its height that keeps changing even though
the same amount of text is showed (there is no long line breaking
involved). I think it is distracting and weird but I may be missing
something.
>> This first patch does not do this but it just simplify how those
>> scroll bar are drawn.
>
> Please explain the rationale for each part of this change. It isn't
> obvious, at least not to me.
While I was trying to understand how the scroll bar and its handle are
drawn, I read this code where drawing a scroll bar is:
1- Fill the rectangle area above the handle (with background)
2- Fill the rectangle area of the handle (with foreground)
3- Fill the rectangle area below the handle (with background)
It seems more "natural" to me to:
1- Fill the entire scroll bar area (with background)
2- Fill the handle area on top of it (with foreground)
--
Manuel Giraud
next prev parent reply other threads:[~2023-04-07 7:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 6:46 bug#62707: 30.0.50; [PATCH] Non toolkit scroll bar handle Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-07 7:10 ` Eli Zaretskii
2023-04-07 7:55 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-04-07 9:14 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-07 10:40 ` Eli Zaretskii
2023-04-07 10:34 ` Eli Zaretskii
2023-04-07 11:56 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-07 12:56 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-07 13:46 ` Eli Zaretskii
2023-04-07 13:57 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-08 0:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-08 0:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-08 14:46 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87pm8gdt3q.fsf@ledu-giraud.fr \
--to=bug-gnu-emacs@gnu.org \
--cc=62707@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=manuel@ledu-giraud.fr \
/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).