Rockbox mail archiveSubject: Re: quickscreen changes (was Voice patches)
Re: quickscreen changes (was Voice patches)
From: Stéphane Doyon <s.doyon_at_videotron.ca>
Date: Tue, 09 Oct 2007 20:44:18 -0400 (EDT)
On Tue, 9 Oct 2007, pondlife wrote:
>>> I've been experimenting with my prototype new quickscreen only for a
>>> couple of days. The single most useful thing is the quick,, no fuss
>>> to clock time...
> For sighted users, there's little point in putting a clock onto the quick
> screen as it's already there on the status bar.
Indeed. That's why I was imagining it as a voice/blind oriented context.
The volume control I imagined in there is for voice menus, and the .talk
clip override is for those who can't read the screen obviously. Hmm but
the tracklock / study mode toggle however might be perfectly useful to a
sighted person (if/when I commit that patch). Stil feels like a jumble...
> I wonder if you would be better off with a generic "read screen" function,
> covering the status bar and WPS (ultimately)?
Well speech is very linear. Jus speaking everything back to back isn't
convenient enough. It's already annoying in the Rockbox info screen. It'd
have to be a context in which I can ask for the info I want. The WPS info
could hookup in that context, or maybe as an option in the WPS context
I was going through the statusbar earlier today. Some of it is useful,
like a quick access to the battery level. The play mode is pretty useless:
must be nice to be able to glance at it, but pretty pointless if I have to
ask for it. The shuffle and repeat state: again must be nice to be able to
glance at them, but if I'm two button presses away from that info, I might
as well go to the root menu's context menu. I already have quick access to
those through the quickscreen, and that's what I'm proposing be thrown
away to make room :-).
> Of course, this would need a
> spare button combo,
Yes, I see no way out of that.
> but I'd think a configurable option (maybe "Voice
> menus"?) could help free something up.
Really? Any ideas? I'm really only familiar with button mappings for x5
and e200. X5 is the problematic one of course. I don't see any other
function I can take out. It's down to long RECORD, or a combination with
POWER (which would be acceptable I guess).
-- Stéphane Doyon <s.doyon_at_videotron.ca> http://pages.videotron.com/sdoyon/Received on 2007-10-10