can't change page in viewer using up/down cursor keys, page-up/down

[texworks]

can't change page in viewer using up/down cursor keys, page-up/down

[GoogleCodeExporter]

Works now (as of r.149), thanks!

Now I'm just missing being able to scroll in the preview window using the mouse
wheel. (This works in the editor, and I would have thought that it's automatic 
once
the key maps have been implemented, but that seems not to be the case.)

Original comment by [email protected] on 8 Sep 2008 at 12:26

[GoogleCodeExporter]

In r.150, scroll-wheel support should also work.

Original comment by [email protected] on 8 Sep 2008 at 9:17

• Changed state: Fixed

[GoogleCodeExporter]

Confirmed, thanks!

One last nitpick: the scroll-wheel cannot change the page (same as up/down-keys 
pre-

Original comment by [email protected] on 9 Sep 2008 at 8:25

[GoogleCodeExporter]

Hmm.... yes, I suppose that could be nice, but it's annoying if you mean to 
scroll to the bottom of the page, but 
overshoot ever so slightly, and the view jumps to the next page. (That'd be 
fine in a continuously-scrolled view 
of all the pages, but not good in the current single-page view.) So this needs 
some care.
The equivalent issue with the arrow keys is dealt with by *not* changing to the 
next (or previous) page when the 
key is auto-repeating; it'll only change pages on a new keypress.

Original comment by [email protected] on 9 Sep 2008 at 11:55

• Changed state: Started

[GoogleCodeExporter]

Interesting; I hadn't thought of that. This never bothered me in
kpdf/okular/acroread, even in a fit-to-width view with non-continuous pages. 

I guess my use case is different then: I use the mouse wheel mostly for quickly
browsing the pages and the hand tool for scrolling within pages. If my hand is
already on the mouse to switch to the viewer, I prefer to keep it there (for 
me, the
editor is predominantly keyboard, the viewer mouse-controlled). But I also 
prefer to
move the cursor around as little as possible, so I tend not to use icons at all.

Long story short: if the current behavior is by design, I don't mind. Of 
course, if a
similar compromise as with the arrow keys is possible, that would be great. 
(Maybe:
mouse wheel changes page only in full page view or if the view is already at 
the page
boundary?)

Original comment by [email protected] on 9 Sep 2008 at 1:16

[GoogleCodeExporter]

OK, in r.151 the scroll wheel should change pages if (and only if) there's no 
scroll bar, i.e. the page fits entirely in 
the window. If there's a scroll bar, the wheel will scroll only within the 
page, not jump to other pages.

This isn't necessarily a final decision; let's see how it goes. I'm open to 
further suggestions, but when I tried it 
with the wheel scrolling the page and then jumping to the next page as soon as 
it tries to scroll beyond the edge, 
I found it quite confusing. The scroll wheel doesn't really have an equivalent 
distinction to the auto-repeat vs. 
new keypress case for the arrow keys, but maybe some kind of delay there would 
work, or require several steps 
of the scroll wheel beyond the limit of the scroll bar range.

Original comment by [email protected] on 9 Sep 2008 at 5:03

[GoogleCodeExporter]

Works for me. Thank you very much! 

Although I also like the idea with needing multiple ticks of the wheel for a 
page
change - as if the edge of the page had some 'resistance'. I think the main 
problem
remains: different mice have wildly different tick spacings (compare the Apple 
Mighty
Mouse or the two finger touchpad scroll), so what will feel comfortable with 
one will
be annoying with another.

Original comment by [email protected] on 9 Sep 2008 at 5:10

[GoogleCodeExporter]

OK, I've made one more update (r.152) - the wheel can now flip between pages 
even if there's a scroll bar, but it 
will "hesitate" at the page edge so that you don't accidentally flip pages when 
trying to just scroll to the top or 
bottom of the view.

If there's no scroll bar (e.g., "fit to page") it will still flip through the 
pages with no hesitation.

Let me know if you think this is a reasonable behavior.

Original comment by [email protected] on 10 Sep 2008 at 7:35

[GoogleCodeExporter]

That's fine - the behavior is surprisingly quick to get used to.

Thanks again!

Original comment by [email protected] on 10 Sep 2008 at 2:08

[GoogleCodeExporter]

Glad it works for you. I'm closing this issue as "fixed" now, though I suppose 
we might want to reconsider it 
when alternative views (such as continuous-scrolling, two-up, or others) get 
implemented. Thanks for the 
helpful feedback.

Original comment by [email protected] on 10 Sep 2008 at 2:23

• Changed state: Fixed