Newsgroups: rec.games.int-fiction
Path: news.duke.edu!newsgate.duke.edu!news-hog.berkeley.edu!ucberkeley!newsfeed.stanford.edu!newsmi-us.news.garr.it!newsmi-eu.news.garr.it!newsrm.news.garr.it!NewsITBone-GARR!news.mailgate.org!zur.uu.net!ash.uu.net!world!not-for-mail
From: buzzard@TheWorld.com (Sean T Barrett)
Subject: Re: buzzard 'terp reviews
Sender: news@world.std.com (Mr Usenet Himself)
Message-ID: <GMzAKo.77p@world.std.com>
Date: Sun, 18 Nov 2001 04:17:10 GMT
References: <GMw0C9.6oy@world.std.com> <zSzJ7.18433$AP3.1060010093@newssvr14.news.prodigy.com> <GMz03v.DDD@world.std.com> <XREJ7.13687$my5.1176021088@newssvr21.news.prodigy.com>
NNTP-Posting-Host: sgi01-g.std.com
Organization: The World Public Access UNIX, Brookline, MA
X-Newsreader: trn 4.0-test72 (19 April 1999)
Lines: 14
Xref: news.duke.edu rec.games.int-fiction:66624

Mike Roberts <mjr-underscore@hotmail.com> wrote:
>How about this as a compromise:
>the renderer could internally keep the pages
>separate and never show them such that two pages are on the screen at once,
>but it could keep the scrollbar adjusted so that all previous pages are
>logically part of the scrolling range.

It might be weird, yeah. There's a bit of trickiness with managing
the scrolling range when you resize the window horizontally, still.
I'm leaning towards thinking that the link-to-the-previous-page at
the top, which starts just off the top of the screen, would work
well enough, and is presumably a lot less work.

SeanB
