• Status Closed
  • Percent Complete
  • Task Type Patches
  • Category User Interface
  • Assigned To No-one
  • Operating System All players
  • Severity Low
  • Priority Very Low
  • Reported Version Daily build (which?)
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Rockbox
Opened by animatorgeek - 2009-06-15
Last edited by teru - 2009-11-08

FS#10338 - Add "use morse input " entry to settings menu

This patch adds an entry to the settings menus to set whether the user wants to use the morse code text input screen rather than the main keyboard screen. An entry in the general_settings struct now holds the current morse input bool.

As a result of this change, whenever the user changes between the morse and standard text input screens – either through the menu or the key combo while inputting text – Rockbox will remember that setting across sessions. This makes the menu item a somewhat redundant feature, but still valuable since it doesn’t require remembering an obscure key combination to change text input style.

I applied this patch to revision 21293, but should be generally applicable.

Closed by  teru
2009-11-08 13:29
Reason for closing:  Accepted
Additional comments about closing:   Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407

Committed in r23567.

I think you forgot to upload the patch. :P

Oops, I could have sworn I had attached it. Here it is now:

looks fine except adding a whole menu for 1 setting is not good…. just place it somewhere logical

I know nothing about morse input, but wonder if you need a menu item at all - could it not just remember the last selected mode?

That’s a good point, though part of the reason I wanted to have a menu item is that it’s really hard to remember the button shortcut for switching to the morse screen (at least on the h120) if you haven’t used it in a while.

But yeah, changing it to get rid of the menu item is totally an option. It’s hard to get a feel about whether anyone else has an opinion about how this should work. At any rate, it would be nice if _at least_ the input choice was persistent.

And yeah, I agree, adding a whole menu for one setting is rather extreme. I looked around and I didn’t find a place where I thought it would fit with the other entries. I’ll take a look again.

Okay, here’s a new version. I got rid of the menu entry entirely. Now it just remembers which input mode you last used.

Hi I get the following error on my my 5th gen using this patch (see the image) yes I have used a clean build on this patch.

teru commented on 2009-08-22 13:23

Make the change bit general. not tested well.
* Move relevant defines to settings.h and the other defines to keyboard.c
* Add option item to change the setting under “Settings → General Settings → System” * Enable morse input for some targets that doesn’t have key to change mode in the keyboard
- Needs to change the setting under “Settings → General Settings → System” to change input mode for these targets.

teru commented on 2009-10-06 14:00

Sync to r22983.

teru commented on 2009-11-06 14:08

update patch.
* move #define HAVE_MORSE_INPUT to config-*.h


Available keyboard shortcuts


Task Details

Task Editing