I assume by 'timed' scrolling you're implying an automatic scroll. There is nothing in the preferences about automatic scrolling.
There is the ability to specify the delay between scrolls. That is, you can specify how fast the pages scroll when you push the page down button, and the speed lines scroll when you tap or push the d-pad.
At least FBreader's developer has had the common sense to give the user the choice (old style navbar can be set in preferences).
A Sho said, I was talking about having the os style scrollbar in place of the traditional nav bar. I already have the set the preferences back to the old style, but would be nice to have this in the os style.
Liking the tap to scroll/turn page, makes life easier on the n810, since the +/- buttons can be awkward to use depending on how you hold the IT while reading.
FBReader 0.10.5 is released (March 20, 2009). Changes:
* The migration tool from version 0.8.* has been fixed. If you made an upgrade on your Internet Tablet or desktop computer from 0.8.* to this version, the first opening of your library will take some time. (About 2 minutes on Nokia 810 for my 400-book library.) Please, be patient, the second opening of the library will be as fast as usual.
* An FBReader freeze has been fixed.
* Several text selection related issues have been fixed.
* Desktop debian packages have been updated to avoid a conflict with a version in the standard Ubuntu 9.04 repository.
Autoscroll is the *BEST* feature of MobiReader on my Nokia 9300b--you can tweak it up or down speed-wise as you go along.
I think that having to press a mechanical button to scroll just wears out the button and makes your finger sore. Maybe this is what is preferred by heavy game-players since they seem to have calluses on their thumbs? ;-v
He can at least do it for those who find it helpful but thanks to him anyway for updating this useful app.
Autoscroll can't be implemented cleanly with the current architecture. FBReader's portability is both a blessing and a curse, in this case, it prevents usable autoscrolling (here's a test, turn one full page and watch how long it takes to refresh the screen).
Whatever the developer does or does not think, FBReader + our hardware == no autoscrolling.
Autoscroll can't be implemented cleanly with the current architecture. ... Whatever the developer does or does not think, FBReader + our hardware == no autoscrolling.
Sorry, but I think you are wrong. There is at least one vertical scroller shoot'em'up game for the tablets and it scrolls the whole screen just fine. What makes you think that the current hardware prevents auto-scrolling?
