[PATCH] RFC: ReadActivity fullscreen, paging changes

[Klaus Weidner]

[ replying to myself, sorry about the confusion ]

On Sun, Jan 27, 2008 at 03:32:15AM -0600, Klaus Weidner wrote:
> I had missed the earlier thread, I'll go look for it.
> 
> I think you misunderstood what I changed - the arrow/rocker buttons
> continue to work exactly like they used to. I only added the
> PageUp/PageDown mappings to the 'X' and 'O' game keys and to Fn-Up/Fn-Down,
> these keys previously did nothing at all. So I don't see how this could
> be worse for anyone.

I've now read the old thread, and I think there's some confusion between
a "page" being a screenful versus being the paper sheet to which I've
contributed, sorry.

I agree that PageUp/PageDown should scroll by screenfuls - that's how
evince normally does it but something seems to be going wrong in the
activity. I'll look into it more. Advancing by paper pages can be
useful, for example if you've zoomed in a bit to eliminate margins and
want to read the next page without having to readjust the viewport. Maybe
put that on Home/End (Square/Check) or use a modifier for it?

> > one thing I have seen programs do (which I found slightly annoying, but 
> > tolorable) is to page a screen at a time but go to the top of the page 
> > when crossing a page boundry
> 
> I'd prefer the behavior you describe, but this should be a user choice
> since obviously preferences are different.

Actually, in standard evince the continuous/single page toggle switches
exactly between those two modes.

-Klaus