This is the bug/patch tracker for Rockbox. Click here for more information.
Quick links: Bugs · Patches · Rockbox frontpage
FS#7873 - New keymap for e200's text editor
Attached to Project:
Rockbox
Opened by Thomas Martitz (kugel.) - Sunday, 30 September 2007, 20:20 GMT+2
Last edited by Dave Chapman (linuxstb) - Sunday, 30 September 2007, 20:21 GMT+2
Opened by Thomas Martitz (kugel.) - Sunday, 30 September 2007, 20:20 GMT+2
Last edited by Dave Chapman (linuxstb) - Sunday, 30 September 2007, 20:21 GMT+2
|
DetailsThis (my second) patch changes the keymap of the e200 to a more natural and easier to use one.
Changes: Editor plugin: Remove removing a line with context-menu-button swap the function of power button and left button Keyboard typing screen up/down/left/right for browsing in the characters scrollwheel to move the cursor rec+up to finish editting the line rec+down = backspace I find this much easier to use Suggestions are welcome, since I can imagine, that it can be optimized even more |
This task depends upon
Also, got rid of the rec+up/rec+down: Backspace is REC now and Accept/Done is Hold Select.
* The feature to delete on line via hotkey returned, it's hold select as in the SVN
* In the SVN, the "Do what" menu moved to button_down, I changed it to be button_power. Note: I needed to hack a but, since there is no standard action for the power button. I created an action ACTION_STD_POWER_BUTTON_PRESS, which has no use, except making the button usable in the text editor.
* I changed the button_left function to only cancel editing (aka ignore changes and exit), but it shows a splash when there were unsaved changes
* I mapped the "line options" menu to button_down.
Note2: I planned to map the delete line via hotkey feature to the rec_button, but I didn't implement, since it conflicts with another patch I use. However, if you liked it I'd implement it.
Just a question: I know this patch isn't done in a proper way, which is mainly a result of the text_editor using standard context. But is there any chance for a commit, even if only the keyboard screen changes would get committed?
just a question: is the "dirty hack" preventing this from being committed?
But there's no way for this patch to get in SVN in its current form, it's too hackish and dirty and stuff. Ideally, the text editor should not use standard button context, but define his own, so things can be more flexible on a per-target basis.
so at first text editor must get his own button context
(perhaps I will compare the text editor to plugins that do use their own button context)
and then we can discuss, whether the new behaviour for e200 is wanted or not
perhaps i'm the only one using this patch... well... I like it