Sansa e200/e200R: Keymap change.

[MarcGuay]

A few clinks in the manual...

1)  Recording Screen

Submenu:  Exit Recording Screen. While recording: Stop recording.
Submenu:  Open Recording Settings (see section 9).

- The first entry should be "Power" instead of "Submenu".

2)  FM Radio Screen
 
Power:  Leave the radio screen with the radio playing. Stops the radio and returns to Main Menu.
Submenu:  Displays the FM radio settings menu.
 
- Power should just be "Stops the radio and returns to Main Menu."
- Submenu should be "Returns to the main menu".
- Long-select should be "Displays the FM Radio Menu"
- Short-select should be "Display the presets list"

I'll post it in flyspray if you want... Just figured you'd be following this thread anyway...

[Llorean]

Could you compile a current manual and check? The manual is updated daily, and I'm nearly certain that I changed some of those at least already.

[MarcGuay]

Not sure exactly how this works but I just checked the November 23rd build of the manual and the errors I mentionned above are still there.

Holler,
Marc

[Llorean]

Alright, I found both problems I think.

The FM keymap is kept in an entirely different place, and handled quite differently, from the rest of the e200 keymaps, so while changing how the keys were defined it didn't affect that part of the manual.

The other one, I'm quite sure I changed locally, but must've somehow reverted or not saved before making one of the commits.

Both changes should be in the next daily version of the manual. If you notice any other errors, let me know, but it's always better to post to flyspray, as many people can fix the manual, and they go to flyspray and look for errors in the manual category.

[terrence1019]

Was there any consideration for adding an option for Preset/Scan to the FM Radio Menu?  

[Llorean]

This thread is about the keymap.

[Nemesis02]

I think a better idea than just changing it for everyone would probably keeping a profile for different players.  Having different players be able to select the profile of key mapping they want, whether it be the old profile or the new one.  A sort of switch and a reboot would be required to commit the changes.  Could be something in the settings that could be changed.

[thomasjservo]

Hi, sorry for arriving late for the party but I have a few comments on the new keymap.

First, I don't have a big problem with it in principle, it's not a huge change and if it makes cross platform developing and use easier, so be it.

That being said the new keymap takes away some of the functionality of the original, specifically on the fly playlisting. By changing the context menu button's function you took this away and I can't find another way to do it.

Is there a work around on this or plans to address this?

[Llorean]

Please read the manual. As I've said in many places, the new keymap is documented. I did not remove ANY functionality. Every "function" that had a button before, can still be accessed.

Try a long-press of select.

[thomasjservo]

Beautiful. I appreciate the quick reply. Thanks.

[MarcGuay]

That's the "Menu" for the Radio part of the code, not really the "Context Menu", and having it on the button that brings up the main menu elsewhere is actually in line with the way Rockbox expects to work, at least right now. Personally, I'm not happy with the overall way the Radio screen works either, but I'd rather figure out a general improvement to the radio screen than start introducing further divergences in how it works right now.

Argh, I really, truly, hate bringing this thread back up to the top of the list, but I was just poking around the menus while writing out the MenuLayoutDiscussion wiki page and noticed that the "FM Radio Menu" and "Recording Settings" screens are brought up by different buttons, when intuition says it should be the same.  I realize that you think there are bigger issues on the table (and I agree), but in the meantime there is something a little off here.  

Flyspray: http://www.rockbox.org/tracker/task/8542

[Llorean]

This is more or less a "fundamental design problem" I think. As in, they're on different buttons on other targets too, if I recall correctly, and fixing it is more of a case of improving both of those UIs, I think.