Navigation-wise I mean. This is something that's always bugged me, but as 2.0 is imminent I figure I better bring it up sooner rather than later.
* The arrow keys scroll the menu rather than select. This is incorrect and makes the menu impossible to use with the keyboard alone.
* ENTER doesn't choose. Instead I have to click with the mouse. Again, this makes the menu impossible to use by keyboard alone.
Mouse navigation is fine with a mouse, but when all you have is a touchpad (as on my netbook), it's usually easier just to use the keyboard. Unfortunately I can't do so with the PAP. What I'd suggest is the following key setup:
* Arrow keys should change selection. Pressing -> while in the app menu should switch to the links and
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
It looks like "focus" only occurs at the mouse pointer.
I'd like to see the TAB button do something, too - there are two main areas in the menu, the apps on the left and the menu icons on the right. TAB could switch focus to either area, or could take focus from the apps area to the menu icons one at a time.
Of course there are hotkeys for the menu icons (Alt+D for the Documents, Alt+M for Music) but they don't seem to work for 1.5!
I guess that's a bug report. The Hotkeys work in PAP 1.1, but not in 1.5.
I made this half-pony, half-monkey monster to please you.
I never really considered it, but now that you brought it up I totally agree.
this isn't ada compliant. I didn't think of that.
Is it hard to recode the keyboard shortcuts? There are Mac & PC differences.
With just the mouse, it's universal.
Don't be an uberPr∅. They are stinky.
Some people have a harder time using the mouse, due to disabilities.
I made this half-pony, half-monkey monster to please you.
American Disabilities Act in the USA, which wants everything on the net to be complient for deaf/blind/etc folks so that if it is using standard html coding, it's typeable by the braille machine or played outloud by a reader. Or I suppose just keyboard use for the arthritic/manually incapacipated.
Don't be an uberPr∅. They are stinky.
I was wondering what ada meant!
With my corporate background, I tend to interpret abbreviations like that only if they are capitalized.
I made this half-pony, half-monkey monster to please you.
for the menu to support normal windows menu keyboard controls.
Is it possible with the current code without too much effort or is it a really big deal?