From: Yuri Khan <yuri.v.khan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>,
politza@hochschule-trier.de, Tassilo Horn <tsdh@gnu.org>
Subject: Re: Displaying scrollable images in a grid-layout
Date: Wed, 15 Apr 2015 23:02:00 +0600 [thread overview]
Message-ID: <CAP_d_8VNABZQxzJV6QrGFkcxWp7GMVhrfW7_Z5YypZdAB7DA1A@mail.gmail.com> (raw)
In-Reply-To: <83k2xd9w4d.fsf@gnu.org>
On Wed, Apr 15, 2015 at 10:47 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> However, I believe the threshold where pixel-based scrolling and
>> glyph-row-based scrolling meet should be when at least two full glyph
>> rows fit in a window; this way, after the scroll, the previous row is
>> still visible, providing some continuity.
>
> If you really meant "at least", then this means no threshold at all,
> because obviously we have to, and already do, provide pixel-based
> scrolling when a glyph row does NOT fit in the window. Right?
When a glyph row does not fit in the window: pixel-based scrolling.
When between one and two glyph rows fit: pixel-based scrolling,
because otherwise the previous row would disappear without a visual
indication where it went.
When more than two full glyph rows fit, that’s where row-based
scrolling stops being disorienting for me.
When fifty glyph rows fit the window, there is no practical difference
between pixel-based and row-based scrolling in terms of visual
feedback.
“No threshold at all” and “pixel-based scrolling when a row does not
fit” would imply pixel-based scrolling always, without regard to rows.
(Most graphical web browsers do exactly that, and I have no problems
with that; but, as you said, that would be a big change to the overall
design.)
next prev parent reply other threads:[~2015-04-15 17:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 8:06 Displaying scrollable images in a grid-layout Andreas Politz
2015-04-13 14:57 ` Eli Zaretskii
2015-04-13 19:35 ` Andreas Politz
2015-04-13 20:27 ` Eli Zaretskii
2015-04-14 13:29 ` Tassilo Horn
2015-04-14 14:11 ` Stefan Monnier
2015-04-14 14:43 ` Tassilo Horn
2015-04-14 20:04 ` Stefan Monnier
2015-04-14 22:15 ` Rasmus
2015-04-14 14:51 ` Eli Zaretskii
2015-04-14 19:24 ` Tassilo Horn
2015-04-15 2:37 ` Eli Zaretskii
2015-04-15 4:17 ` Yuri Khan
2015-04-15 16:05 ` Eli Zaretskii
2015-04-15 16:35 ` Yuri Khan
2015-04-15 16:47 ` Eli Zaretskii
2015-04-15 17:02 ` Yuri Khan [this message]
2015-04-15 17:33 ` Eli Zaretskii
2015-04-15 18:26 ` Andreas Politz
2015-04-15 19:31 ` Stefan Monnier
2015-04-14 14:56 ` Eli Zaretskii
2015-04-14 19:29 ` Andreas Politz
[not found] ` <8738424igv.fsf@hochschule-trier.de>
2015-04-15 2:41 ` 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=CAP_d_8VNABZQxzJV6QrGFkcxWp7GMVhrfW7_Z5YypZdAB7DA1A@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=politza@hochschule-trier.de \
--cc=tsdh@gnu.org \
/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).