search for: arrowkey

...hile such change should be as less traumatic as possible for current > users. In my opinion, this would be better addressed with a conditional directive than an outright change in current behavior. Since it only affects (vesa)menu.c32, it should begin with "MENU ", perhaps "MENU ARROWKEY" (perhaps someone will think of another alternate behavior in the future). It should also accept 1 optional parameter to turn it on or off. When not present, it should turn the new behavior on. -- -Gene

...less traumatic as possible for current > > users. > > In my opinion, this would be better addressed with a conditional > directive than an outright change in current behavior. Since it only > affects (vesa)menu.c32, it should begin with "MENU ", perhaps "MENU > ARROWKEY" (perhaps someone will think of another alternate behavior in > the future). It should also accept 1 optional parameter to turn it on > or off. When not present, it should turn the new behavior on. > > -- > -Gene What exactly do you mean with "When not present, it s...

...ble for current >> > users. >> >> In my opinion, this would be better addressed with a conditional >> directive than an outright change in current behavior. Since it only >> affects (vesa)menu.c32, it should begin with "MENU ", perhaps "MENU >> ARROWKEY" (perhaps someone will think of another alternate behavior in >> the future). It should also accept 1 optional parameter to turn it on >> or off. When not present, it should turn the new behavior on. >> >> -- >> -Gene > > > What exactly do you mean with...

...> > users. >>> >>> In my opinion, this would be better addressed with a conditional >>> directive than an outright change in current behavior. Since it only >>> affects (vesa)menu.c32, it should begin with "MENU ", perhaps "MENU >>> ARROWKEY" (perhaps someone will think of another alternate behavior in >>> the future). It should also accept 1 optional parameter to turn it on >>> or off. When not present, it should turn the new behavior on. >>> >>> -- >>> -Gene >> >> >&g...

> Since keystrokes were brought up, this seems like a reasonable time to > make the following seemingly simple-to-implement feature request: > > Navigating a multi-level menu structure seems to require use of > UP/DOWN/ENTER/ESC. It would be easier to quickly search/navigate if it > could be done with fingers stationed on the arrow keys so that the eyes > can stay focused

Since keystrokes were brought up, this seems like a reasonable time to make the following seemingly simple-to-implement feature request: Navigating a multi-level menu structure seems to require use of UP/DOWN/ENTER/ESC. It would be easier to quickly search/navigate if it could be done with fingers stationed on the arrow keys so that the eyes can stay focused on the screen. Current