From: "grischka" <grishka@gmx.de>
To: "Kim F. Storm" <storm@cua.dk>
Cc: emacs-devel@gnu.org
Subject: Re: vertical scrollbar error on MS Windows
Date: Wed, 21 Feb 2007 15:02:58 +0100 [thread overview]
Message-ID: <007301c755c1$57446e20$2446fe91@j4f3n1> (raw)
In-Reply-To: m3irdwx7bp.fsf@kfs-l.imdomain.dk
Kim F. Storm writes:
> "grischka" writes:
>
> > Hi there,
> >
> > Here is another fix for the scrollbars. From the approach
> > it calculates the thumb length once on mouse down and
> > then leaves bar parameters alone during dragging. Patch
> > for w32term.c is in the attachement.
>
> Thank you.
>
> But I think this change is too radical at this time.
>
> Counting lines like that does not always give a
> correct answer - e.g. if there are overlays / images
> in the buffer.
>
Shure, but then it does not really matter whether the
slider is a bit longer or shorter in cases.
It is important on the UI level however, that there is a
reliable relation between slider position and text view,
i.e. that the visual feedback is consistent with the hand's
movement. Otherwise it feels like a loose handle bar on
a bicyle.
For example even with your patch there is still the problem
that sometimes the slider shrinks in the end as supposed,
while with other files it remains stuck and it's not possible
to see the last line. Or sometimes the slider shrinks itself
on mouse down already such that mouse points into void. Etc.
> I think we need to rethink the whole scrolling functionality
> after the release (also for the other ports).
No objection to that. Also I'd suggest to bind Ctrl-up/down
as standard for single line scrolling. This is really missing,
the more as long as sliders dont work so well ;)
Thanks,
-- grischka
next prev parent reply other threads:[~2007-02-21 14:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 0:24 vertical scrollbar error on MS Windows grischka
2007-02-21 8:07 ` Kim F. Storm
2007-02-21 14:02 ` grischka [this message]
2007-02-21 19:01 ` Stefan Monnier
2007-02-21 23:36 ` grischka
2007-02-26 19:39 ` Stefan Monnier
2007-02-27 19:19 ` grischka
2007-02-27 20:44 ` David Kastrup
2007-02-27 22:56 ` Stefan Monnier
2007-02-28 19:45 ` grischka
2007-02-28 21:45 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2007-02-28 20:01 grischka
2007-02-28 20:54 ` Lennart Borgman (gmail)
2007-03-01 9:11 ` David Kastrup
[not found] <b5accf970702131432t76036b4erb72cbe4d86e11077@mail.gmail.com>
[not found] ` <er4kem$ce7$1@sea.gmane.org>
2007-02-19 14:58 ` Kim F. Storm
2007-02-19 16:13 ` Juanma Barranquero
2007-02-19 22:39 ` Kim F. Storm
2007-02-19 23:01 ` Juanma Barranquero
2007-02-19 23:16 ` Nick Roberts
2007-02-19 17:03 ` Lennart Borgman (gmail)
2007-02-19 22:54 ` Peter Tury
2007-02-22 15:07 ` Stephan Hennig
2007-02-22 15:56 ` Jason Rumney
2007-02-22 16:52 ` Kim F. Storm
2007-02-22 17:00 ` Stephan Hennig
2007-02-22 17:28 ` Kim F. Storm
2007-02-22 23:35 ` Stefan Monnier
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='007301c755c1$57446e20$2446fe91@j4f3n1' \
--to=grishka@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
/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).