summaryrefslogtreecommitdiff
path: root/firmware/target
diff options
context:
space:
mode:
authorDana Conrad <dconrad@fastmail.com>2021-03-14 14:03:00 -0500
committerWilliam Wilgus <me.theuser@yahoo.com>2021-05-24 02:30:09 +0000
commit10d199f9d5bf85136211c0811e29679787343375 (patch)
tree6fd57cb5cf8bac3e23b65dfd469d57bee969e6fc /firmware/target
parentb66990cf77b1726b2cda1e9225a06df71738d46b (diff)
downloadrockbox-10d199f9d5bf85136211c0811e29679787343375.tar.gz
rockbox-10d199f9d5bf85136211c0811e29679787343375.zip
Allow Softlock to happen in most contexts
All this tested on erosq, I'm not sure if this will break on other targets or if there is a reason this shouldn't be done. apps/menu.c: Added CONTEXT_MAINMENU|ALLOW_SOFTLOCK in do_menu(), this allows the user to lock the keys in most places within the main menu tree. apps/tree.c: Added CONTEXT_TREE|ALLOW_SOFTLOCK in dirbrowse(), this allows locking the keys in most other contexts not covered by the above. Notable exceptions I've found that still cannot be locked: View Playlist, any settings change screen (ex. Shuffle No/Yes, Volume Select dB) Adding fix for Advanced Key Lock feature brought to light by this change in apps/action.c. Expected behavior for Advanced keylock is now (according to my testing here): Volume: Can be exempted from keylock anywhere Skip/Scrollwheel: Can only be exempted in WPS Seek: Can only be exempted in WPS Play: Can only be exempted in WPS Backlight exemption is same except the Volume exemption doesn't work outside the WPS, but I don't believe that is due to this change. Change-Id: Ifa3d1a03cf4884520a37dd91ed53a825cdb66778
Diffstat (limited to 'firmware/target')
0 files changed, 0 insertions, 0 deletions