[bookport] Re: BUG OR FEATURE, SOME FILES WON'T NAVIGATE BACKWARD?

  • From: buhrow@xxxxxxxxxxxxxxxxxxxxx (Brian Buhrow)
  • To: bookport@xxxxxxxxxxxxx
  • Date: Fri, 16 Sep 2005 15:12:08 -0700

        Hello Sarah.  Yes, I think that's the same behavior.  Gary Wunder says
he's seen it too.  His comment suggests that APH knows about the problem
and has tried to address the issue, at least with the page motion keys.
However, my experience is that backward navigation, when it doesn't work,
doesn't work for all key strokes except the one which moves you the
furthest distance.  So, for texts which are indexed by line and page, you
can move backward by page, but not by line. For texts indexed by line, page
and section, you can move backward by section, but not by page or line.
This is true in indexed MP3 files as well.
        You are also correct that this behavior only occurs when actively
reading, not when idle.
-Brian
On Sep 16,  4:46pm, "Sarah Cranston" wrote:
} Subject: [bookport] Re: BUG OR FEATURE, SOME FILES WON'T NAVIGATE BACKWARD
} Brian,
} 
} I don't know if this is relevant, but I have noticed an issue I call the 
"sentence issue".  <Smile>
} This happens when a sentence has an extra period at the end of it.  If you 
read to the next sentence, then try to back up by sentence, the BP seems to 
hang on that period, or whatever it is, and won't go back any further.  Note 
that this only happens to me when the unit is playing.  When it is stopped and 
I press the 1 key, I sometimes hear nothing when it gets to that phantom period 
thing. Does your BP act normally in these files when it is stopped?
} 
} Sarah
} 
} 
} -----Original Message-----
} From: bookport-bounce@xxxxxxxxxxxxx
} [mailto:bookport-bounce@xxxxxxxxxxxxx]On Behalf Of Brian Buhrow
} Sent: Friday, September 16, 2005 3:28 PM
} To: bookport@xxxxxxxxxxxxx
} Cc: buhrow@xxxxxxxxxxxxxxxxxxxxx
} Subject: [bookport] BUG OR FEATURE, SOME FILES WON'T NAVIGATE BACKWARD?
} 
} 
}       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
} 
} 
>-- End of excerpt from "Sarah Cranston"



Other related posts: