From: Neon John <johngd_at_bellsouth.net>
Date: Fri, 22 Aug 2003 14:51:12 -0400

On Fri, 22 Aug 2003 11:44:28 +0200 (CEST), Daniel Stenberg <daniel_at_haxx.se>
wrote:

>Hey
>
>Since there have been a lot of talk about a revised keymapping, I and Linus
>sat down and updated my NEWKEYS document.
>
>This is the approach we suggest (limited to (fm)recorder-models).
>
>Some of the highlights include:
>
> o Main menu always on F1
> o Do not exit main menu with F1, only OFF

Not sure about this. I like being able to toggle the menu off and on with the
F1 key.

> o F3 is for context-sensitive menus in all screens
> o F2 is the new "User Menu" for customizable/plugin stuff
> o no more "quick-screens"
> o moved keylock combo

I like it. I assume you mean providing a single key keylock?

I've had another thought about keylock. Most of the time when I have the
keyboard locked, the reason I unlock it is to change volume. How about
providing a user-selectable option to have a long, say 3 or 4 second, volume
key press override the lock. That would accomplish two things. One, it would
let me change volume without having to do the unlock sequence. Two, it would
prevent accidentally operating the other keys when groping for the volume
while driving, in the dark, etc. I have a bad habit of hitting the track
forward or back when looking for the volume controls.

I would, of course, want to disable this feature for when I want to totally
lock the keyboard so a user-selectable option would be a necessity.

>
>We also started on a minor refactoring of the menu code to make it easier to
>use the functions for all sorts of menus, without getting a lot of extra cruft
>brought to all menus (for example the f2/f3 key handling).
>
>Feel free to comment!

---
John De Armond
johngdDONTYOUDARE_at_bellsouth.net
http://bellsouthpwp.net/j/o/johngd/
Cleveland, Occupied TN

Received on 2003-08-22