An improved scrollbar
the current scrollbar cannot be used practically in a long book. So it should be improved.
Suggestion:
1) multiple scrollbar, each of them is having different range.
2) to scroll through the current chapter, but then when it is at the bottom of the chapter, you click the "down arrow" or press the "page down", then it jumps to the next chapter (and of course the scrollbar will go to the beginning of that chapter instead). To press once page down is much more convenient than the current method: to press down/page down every time I want to move to some other place.
3) One way that Logos might be able to do is this: there is a box at the top of the window indicating the passage I want to study, right? Then that one is the range of the scrollbar. BUT, currently the location is keep changing as you move along the passage.
- like acrobat, to put a "drag" mode, that can use a "hand" to move the screen.
Kolen
shared this idea
-
David Loo
commented
I definitely agree with a non-linear scroll-bar in Windows. As it is now, simply dragging the scroll-bar by a tiny amount can cause you to skip dozens of chapters (especially with a large book). Drag-mode will also be very useful.
-
Steve Coward
commented
Agree with John . . . it might also be nice to have a "paging" format (similar to the kindle-pc interface or many of the ebook readers for the iphone)
-
John Duffy
commented
I'm not sure that multiple scrollbars are the answer. I would suggest a non-linear scrollbar, such that a given movement near the existing location is insensitive and only moves the text position a little, but as one moves further away from the current location, it becomes much more sensitive and moves in larger sections for the same mouse movement. This is a bit like how mouse sensitivity is enhanced in an operating system.
Also, I would suggest that something needs to be done about the breadcrumbs, where proliferation of them means that one cannot click above or below the cursor to page down, as one hits breadcrumbs instead. Some windows don't respond to PageUp/PageDown either, making it worse.