[bookport] BUG OR FEATURE, SOME FILES WON'T NAVIGATE BACKWARD?
- From: buhrow@xxxxxxxxxxxxxxxxxxxxx (Brian Buhrow)
- To: bookport@xxxxxxxxxxxxx
- Date: Fri, 16 Sep 2005 13:27:44 -0700
Hello. Let me appologize in advance for the length of this message.
Background:
I'm running Bookport, Firmware V2.1, released in June of this year, I
believe.
Description of problem:
I have a number of texts on my Bookport, some gleaned from Daisy
files from Bookshare, some gleaned from the ASCII files on the CDROM which
came with the Bookport, and some indexed MP3 files.
When reading through some of the texts, I find that the 1 and 4 keys
go back to the beginning of the current line or sentence while reading, but
no further, regardless of how often I press the 1 or 4 keys. On other texts,
which appear to be indexed exactly the same
way, repeated use of the 1 or 4 keys while reading causes the reading
pointer to move past the beginning of the current line or sentence, and on to
the
beginning of the previous line or sentence. In all cases, the 7 or 1-4
keys appear to work properly and move backward, from page to page, or
section to section, as advertised in the documentation.
Is there some feature whereby some sort of hierarchical navigational
restriction can get turned on such that only commands which move you backward
through the texts with less granularity take precedence over ones which
move in smaller increments? It is worth noting, that there is never a
problem moving forward through texts, just backward.
At first I thought the problem was that I wasn't hitting the
navigational keys fast enough. The pointer would move back to the beginning
of the selected index point, and them move forward as reading continued.
Then, when I pressed the key again, the pointer would be beyond the
beginning of the selected index point, and so it would move back to where
it was. Then, I discovered some files where the behavior was different.
With those files, when navigating backward, Bookport would move bak to the
beginning of the indicated index point, then, with another key press, it
would move back to the beginning of the previous block.
Has anyone else noticed this inconsistency? Has anyone else noticed
it and figured out what's different? Is there some feature of which I'm
not aware?
-thanks
-Brian
Other related posts:
