Rockbox Technical Forums
Support and General Use => User Interface and Voice => Topic started by: animatorgeek on June 11, 2009, 06:46:07 PM
-
Is there some way to make morse code the default text entry method on the h1x0? If it isn't possible to change it with a setup file or something (which it seems like it should), would it be possible to change it without too much trouble in the source code?
-
Why? Because the key combination to enter Morse code mode is too troublesome?
-
Basically, yes. It would be nice to not have to think about it. It seems like something that should appropriately be a setting in the menus anyway. I would think that each user would almost always want one or the other, and rarely switch between the two. Why, then, require the user to switch every time if they don't like the default?
-
It would be more useful if it were enabled on more targets. I was a little surprised when I switched from an H10 to a sansa c200, and found my beloved Morse code entry gone.
I do agree with you that it should be a configurable option. It is also fantastically nice to type stuff without having to look at the screen or juggle more than two buttons. I expect I may be doing a lot more typing now with the Lua support.
-
I'm actually delving into the code now to try and make a morse code setting in the menus. I think I found how I could make morse code default in a custom build, but I figured why not go all the way and make it user configurable?
-
It would be more useful if it were enabled on more targets. I was a little surprised when I switched from an H10 to a sansa c200, and found my beloved Morse code entry gone.
The problem here is the amount of available and sensible keys or key combos in the virtual keyboard context (c200 actually has quite a lot of buttons compared to e.g. the Ondio but due to how they are laid out it's not easy to find a good mapping).
It doesn't help the thing at all that the Morse screen itself does not use it's own context but reuses the virtual keyboard one so that you need to find unique button mappings for all usual keyboard screen actions + plus something for the switch to and from the Morse screen (that could even be OK as a combo) + plus the Morse key (which is not OK as a key combo, I think). I actually tried finding a button mapping with Morse input enabled for the c200 but it always conflicted with some other already used key (combo) in the keyboard context which resulted in Morse input not working or some unwanted side effects.
I can imagine that solving this will help enabling Morse input on more targets.
-
I actually tried finding a button mapping with Morse input enabled for the c200 but it always conflicted with some other already used key (combo) in the keyboard context which resulted in Morse input not working or some unwanted side effects.
Ah, thank you. Though I am curious what issues came up. Record+down and record+power are free in the virtual keyboard. The H10, same number of buttons as the c200, used a combo to activate morse.
-
I've just submitted a patch to allow the user to set morse mode in the settings menu. At the moment it only works on devices that already have morse mode available, but I wonder: could it make morse mode possible _without_ the key combo? That is, there'd be no key combo to change it while editing but you can choose morse mode in the menus? Is the button combo the only thing preventing morse mode on most platforms?