GNOME Bugzilla – Bug 168449
Mouse Scroll Wheel doesn't scroll through document
Last modified: 2006-08-27 22:15:52 UTC
Version details: 0.1.4 Distribution/Version: Ubuntu Hoary The first time I used evince I clicked on the open page and started spoinning my mouse wheel, expecting the page to change, as it does in Adobe, etc, etc. Didn't work - still on page 1. I'm using 0.1.4. Strangely though, clicking in the thubmnails view bar on the left and scrolling the wheel spirals the view up and down there (to be clear - the view not the page changing). I wouldn't have a clue what the HIG says, but all I want is a way to change the page without using the keyboard.
Hmm it seem to work fine here. If you click on the document and then try to scroll does it work?
No. 1. Open document. 2. Click on first page 3. Spin middle mouse wheel 4a. If page is not completely displayed, page scrolls down to bottom, then stops 4b. If page is completely displayed (ie best fit) nothing happens 5. Click on thumbnail column 6. Spin mouse wheel 7. Thumbnail view changes (page selected does not, which is fine btw) Notes: I'm using Evince 0.1.4 on Ubuntu Hoary. I have tried multiple documents. I am a daily user of adobe acrobat pro at work.
Oh I see now. Bryan, should mouse wheel cycle between pages when you reach bottom/top? I tend to think it shouldnt. (but it obviously should when we implement continous mode)
Marco, agreed. It should scroll to the bottom of a page, but not beyond (unless of course continuous mode). There's no way to give a decent resistance to flipping pages like this. We've tried this in many different places like edge resistance on virt. desktops and the like and it just doesn't work out well enough in nearly every case. Most tests with this system end up with users flipping when they don't mean to, getting confused, then fighting the resistance to flip back and getting frustrated. :-( Watch bug 164597 for continuous scrolling which will allow you to use the mouse wheel to scroll all the way through a document.
*** Bug 152555 has been marked as a duplicate of this bug. ***