- Status Closed
- Percent Complete
- Task Type Patches
- Category User Interface
- Assigned To No-one
- Operating System Another
- Severity Low
- Priority Very Low
- Reported Version Daily build (which?)
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#10683 - Cowon D2 track skipping on hold
rev23223
In Cowon’s OFW was function,that sets +\- buttons as next\prev track while keys are on hold.
That’s implemention of all this on rockbox (soon will add another types of control,as there described:
http://www.iaudiophile.net/forums/showthread.php?t=28467 ).
In fact,this is rework of FS#9875 with adding of setup menu.
Closed by shotofadds
2009-11-11 20:33
Reason for closing: Duplicate
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
2009-11-11 20:33
Reason for closing: Duplicate
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
Superceded by FS#10698
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
I agree - hold should disable keys, not change their functionality.
(updated)
Found bug in MENU button,thinking about how workaround it.
When doing it in “normal” way(i.e.not that insane text in keypad config)-it won’t work anymore.%)
Okay,stopping that FS#.
I actually support this idea and think it’s a case where an option is desirable - indeed it should be disabled by default. It’s not “configurable keymaps” per se, it’s just enabling/disabling a feature.
I can’t see what’s wrong with making HOLD+<key> perform an action if the user has specifically enabled an option to make it do so.