But David, you would KNOW if you had file advancement on. Let's say you're
listening to an audiobook separated into files:
1_chapter 1.mp3
2_chapter 2.mp3
...etc.. You finish chapter 1 and hear, Chapter 2, the journey
of...whatever. You listen to that and then arrive at "Chapter 3, The final
mystery". You're about halfway through that and then you suddenly think,
hey, what am I listening to? I mean, let's get serious. And if you really
forget what book you're listening to, it takes about 2 keystrokes to find
out, as opposed to always having to wait for the file name to be announced
when you don't really need it. I agree, some might want an option like
"announce new file name when advancing to it with audo advance" from the
settings menu...but stuff like that could clutter things up to much. I am
sure there are those, for instance, who hate the fact that the power
movement commands are what they are, and wish you could change them to
different keys. Well, mostly every user who uses them will agree that they
are very logically placed; thus, they cannot understand how anyone can find
it hard to use the power movement commands. This is my feeling on this
situation. APH obviously stopped saying file names with the status command
for a reason.
----- Original Message -----
From: "David Allen" <wd8ldy@xxxxxxxxxx>
To: <bookport@xxxxxxxxxxxxx>
Sent: Saturday, January 28, 2006 5:14 PM
Subject: [bookport] Re: file name
Hi Grant and list:
I'm glad you raised the question. Please consider the following scenario:
You are in a folder containing several files. You have set automatic file advance to yes. Suppose you've listened for an hour or so. Now you'd like to know where you are. You can press 5 to get the time. Suppose it says something like 5:40. This tells you you are 5 minutes forty seconds into the file, but what file? But you know you've been listening for longer than that. Remember, I said you've listened for an hour or so. How is this possible? Well, it is possible because you have obviously got to the end of the file you were originally in and advanced on. But how far on have you advanced? So no, you don't just *know what you're listening to. Having the filename back in the stats would leave you in no doubt. Some of us know how valuable this is because we remember when it used to be there.
Cheers,
Dave
----- Original Message ----- From: "Grant Hardy" <granthardy@xxxxxxxxx>
To: <bookport@xxxxxxxxxxxxx>
Sent: Sunday, January 29, 2006 1:53 PM
Subject: [bookport] Re: file name
Not meaning to be rude, but wouldn't you generally know what you're listening to though? :-)
----- Original Message ----- From: "Chris G" <chrisg@xxxxxxxxxxxxxxxx>
To: <bookport@xxxxxxxxxxxxx>
Sent: Saturday, January 28, 2006 6:54 AM
Subject: [bookport] Re: file name
How about putting the amount in the settings keypad and put the filename back in the stats key. I miss that and it would be nice.
On Sat, 28 Jan 2006 08:33:30 -0500 "Lou Kolb" <loukolb@xxxxxxxxxxx> wrote:
Actualy, I think they removed it to make room for the amount of space left
on the card. As I recall, they couldn't have both. I like being able to
find out how much room is left on the card but I also wish there were a way
to get the name of the current file. I can't tell you how many times I've
been deep into a book but just couldn't recall the exact title. Of course
it is possible to simply move up or back 1 file and then return to the one
in question with the star or pound keys and get the file name that way. Lou
----- Original Message ----- From: "Grant Hardy" <granthardy@xxxxxxxxx>
To: <bookport@xxxxxxxxxxxxx>
Sent: Saturday, January 28, 2006 2:37 AM
Subject: [bookport] Re: file name
> It used to be there but cluttered stuff up too much thus it was > removed.
> Chances are you know what file you're reading. :-)
> ----- Original Message ----- > From: "Chris G" <chrisg@xxxxxxxxxxxxxxxx>
> To: <bookport@xxxxxxxxxxxxx>
> Sent: Friday, January 27, 2006 9:18 PM
> Subject: [bookport] file name
>
>
> > hi, can we have the file name of the book we are reading in the > > extended
> > stats command.
> >
> > Thanks
> >
> > -- > > Chris G <chrisg@xxxxxxxxxxxxxxxx>
> >
> >
>
>
__________ NOD32 1.1385 (20060128) Information __________
This message was checked by NOD32 antivirus system. http://www.eset.com
-- Chris G <chrisg@xxxxxxxxxxxxxxxx> Dogs that bark at a distance never bite. -English Proverb.
