Welcome to the Rockbox Technical Forums!
Really amazing job, amachronic! As for the discussion about keymaps (@cereal_killer and @diegopau), here's what works well for me. My main expectations/requirements were (iirc):Be able to stop playback by long pressing the power button from anywhereGet back to WPS by pressing Play/PauseBe able to scroll menus to the left/right to quickly see longer text strings that get cut off (not supported by the current keymap)See current playlist from WPS with single button press And be able to change volume by touchReturn to browser from WPS with single button pressConsistent activation of context menu in WPS/tree contextI left the Repeat-AB-Start/End button mapping and pretty much everything else unchanged at the moment. If anyone's interested in seeing the keymap, I can put it up on Gerrit. It only requires pretty minor adjustments compared to the current one though..
Quote from: chris_s on October 22, 2021, 12:21:16 PMReally amazing job, amachronic! As for the discussion about keymaps (@cereal_killer and @diegopau), here's what works well for me. My main expectations/requirements were (iirc):Be able to stop playback by long pressing the power button from anywhereGet back to WPS by pressing Play/PauseBe able to scroll menus to the left/right to quickly see longer text strings that get cut off (not supported by the current keymap)See current playlist from WPS with single button press And be able to change volume by touchReturn to browser from WPS with single button pressConsistent activation of context menu in WPS/tree contextI left the Repeat-AB-Start/End button mapping and pretty much everything else unchanged at the moment. If anyone's interested in seeing the keymap, I can put it up on Gerrit. It only requires pretty minor adjustments compared to the current one though..Your keymap looks pretty good to me, it's a bit more polished and thoughtful than what I spewed out. (Nice graphics, by the way!) I'll play with it a bit more over the weekend, but in all likelihood I'll merge it.
{ ACTION_TREE_ROOT_INIT, BUTTON_LEFT|BUTTON_REPEAT, BUTTON_LEFT }
*actionptr = ACTION_STD_MENU;
I don't know if this is possible, but if the touchbar can have different assignations for sliding up/down and tapping up / tapping down, that would give us 2 extra buttons to assign.
Backlight on Hold. This setting controls the behavior of the backlight when the Hold switch is toggled. If set to Normal the backlight will behave as usual. If set to Off the backlight will be turned off immediately when the Hold switch is engaged and if set to On the backlight will be turned on and stay on while the Hold switch is engaged.
(...) Except the screen turning off when locking (press power button to lock the buttons). Iirc the default was the screen turning off when locked but it's not the case here. I looked in the manual and suppousdly there's an option for that. 8.4 Display -> LCD Settings.Quote Backlight on Hold. (...)That option is simply missing from the M3K display menu. The power button just locks the buttons and you have to wait for the screen timeout to turn it off. And long pressing power turns the system off. Any ideas?
Backlight on Hold. (...)
I do think that behavior (turning screen off right away) is better but the M3K doesn't have a hold switch, it has a software lock aka. "softlock." Unfortunately it doesn't work the same way a hold switch does. I had a notion to make it work more like the hold switch but wasn't motivated enough and the code was too confusing. You might want to open a feature request on the bug tracker, just so it doesn't get totally forgotten.Also, that option shouldn't be in the manual since it's only for devices with a physical hold switch.
Hi,I noticed the following behavior related to the "Default Sleep Timer Duration" setting. This might not be M3k related, but for Rockbox in general, I don't know.I created a shortcut for that setting. So now I can change it from:A - Shortcuts => Default Sleep Timer DurationB - Settings => General Settings => Startup/Shutdown => Default Sleep Timer Duration.Now, in the case that the timer is already running: If I change the duration from location A, then the change doesn't have effect immediately, i have to stop the timer and start it again. If I change the duration from location B then it applies instantly, so for instance if the timer was running for 30 minutes and now I set the value for 1 hour it will immediately start counting down from 1 hour.I find this strange so I think it might be considered a bug. Also it is useful if the change is immediate, because I can't add a shortcut to start/stop the timer.
[shortcut]type: timedata: sleep 10name: Sleep in 10[shortcut]type: timedata: sleep 20name: Sleep in 20[shortcut]type: timedata: sleep 0name: Disable Sleep Timer
Page created in 0.086 seconds with 16 queries.