[bookport] Re: Usability of the Lock Function

  • From: "Barrett, Don" <Don.Barrett@xxxxxx>
  • To: <bookport@xxxxxxxxxxxxx>
  • Date: Tue, 3 Aug 2004 10:05:19 -0400

A simple mnemonic way of doing this would be to have one beep for lock =
and two for unlock, corresponding to the one and two syllable words =
themselves.

Don



-----Original Message-----
From: bookport-bounce@xxxxxxxxxxxxx
[mailto:bookport-bounce@xxxxxxxxxxxxx]On Behalf Of Jerry Neufeld
Sent: Tuesday, August 03, 2004 9:55 AM
To: bookport@xxxxxxxxxxxxx
Subject: [bookport] Re: Usability of the Lock Function


agree! I have had the same problem, often thinking the BookPort was =
locked
when, instead, it was merily reading along in my pocket.

Jerry


----- Original Message -----=20
From: "Judith M. Dixon" <jdix@xxxxxxx>
To: "Bookport@Freelists. Org" <bookport@xxxxxxxxxxxxx>
Sent: Tuesday, August 03, 2004 6:57 AM
Subject: [bookport] Usability of the Lock Function


> Hi,
>
> I have another thought for the lock function.  I know it has been
> discussed a lot here but I think an improvement would be to have the =
lock
> feature beep when it is actually being locked and unlocked.  I often
> remember to lock my unit after I take my headphones off, I lock it, =
then
> press a button to see if I did it, if it doesn't beep, I may have =
started
> it playing and now run the risk of locking it on.  So I have to get =
out
> the headphones to see what state I have left it in.  Well, you get the
> idea.  An external confirmation that it is locked would be great.
>
> Judy
>
>
> ************************************************************
> *  Judith M. Dixon                     jdix@xxxxxxx        *
> *  Consumer Relations Officer          (202) 707-0722      *
> *  National Library Service            (202) 707-0712 fax  *
> *     for the Blind and                                    *
> *     Physically Handicapped                               *
> *  Library of Congress                                     *
> *  Washington, DC 20542                                    *
> ************************************************************
>
>



Other related posts: