91
User Interface and Voice / Re: A shortcut that requires a name
« Last post by iPodVT on June 06, 2025, 11:52:10 AM »Please ignore my immediately preceding post - my brain is fuzzy and I made some misstatements re the 'required' and 'ignored' conditions. My apologies.
92
User Interface and Voice / Re: A shortcut that requires a name
« Last post by iPodVT on June 06, 2025, 11:37:08 AM »I deleted the original content of this posting because I had made too many misstatements re 'ignored' and 'required'. Sorry about that.
93
User Interface and Voice / Re: A shortcut that requires a name
« Last post by chris_s on June 06, 2025, 10:20:24 AM »Looks like the manual needs to be updated. Note that a bit further down it explains, for the shortcut type 'time' specifically, that a name is required, unless data is 'sleep' and it is not followed by a number.
Having said that, it seems to make sense to change the code, so that some default value is displayed in all cases, when a name hasn't been provided.
Having said that, it seems to make sense to change the code, so that some default value is displayed in all cases, when a name hasn't been provided.
94
Rockbox Utility / RTC on iRiver H120
« Last post by Datman on June 06, 2025, 03:41:30 AM »Hi all
I have updated my H120 with a 64GB SD card. To do it, I have also updated RockBox to v4.0. Now my RTC mod doesn't work anymore. What do I have to do to restore it?
Thanks
Gianluca
I have updated my H120 with a 64GB SD card. To do it, I have also updated RockBox to v4.0. Now my RTC mod doesn't work anymore. What do I have to do to restore it?
Thanks
Gianluca
95
Hardware / Re: Sansa e200v2 (e280v2): file transfer problems in Rockbox, works in OF
« Last post by bahus on June 06, 2025, 02:08:41 AM »Oddly enough that seemed to work alright for me.
Just means it's some hardware issue in my unit. No need in further testing - filesize doesn't matter. Thanks for testing!
96
Hardware / Re: Sansa e200v2 (e280v2): file transfer problems in Rockbox, works in OF
« Last post by Zakalwe on June 06, 2025, 01:32:41 AM »What does bother me - unstable writes on SD card by rockbox itself. Does it work reliably for you? Can you for instance copy/paste inside rockbox some big amount (500Mb+) of data on your SD card.
Oddly enough that seemed to work alright for me. I copied around some 1.1GB, testing different directions (SD->SD, SD->internal, internal->SD), no crashing. Now that I think of it, it was a folder of mp3s, i.e. small files - I will try with some big file as well.
97
Theming and Appearance Customization / Re: Need to Remove Messed up Themes
« Last post by delta on June 05, 2025, 02:13:18 PM »Well that’s the thing. Is the mono version don’t have any viewports for the back drops. So the color just defaults to whatever the user set color is. The VFD and tripod series were more unique so they have every viewport customized.
98
Theming and Appearance Customization / Re: Need to Remove Messed up Themes
« Last post by Dook on June 05, 2025, 12:19:31 PM »I basically only understand the basics. If you could give me an example that would really help id also like to make an alt version with a album art display while srinking and rearranging a few viewports.
I've never previously done this so I don't know whether or not it would work. At its most basic, my idea was to place some color specs in a text file (e.g. a file named colors.txt whose first line might be FF0D30), and then retrieve and apply the color in that first line via %Vf(%ft(colors.txt,0)).
But it sounds like Dook has some more well thought-out methods in store for us.
I would envision it working more like CSS variables, where each line in a colors.txt file would have a descriptive title and then the colour after like "status_bar_title_color:ff0000". These would then be called with a new tag for background and foreground colours like %sB(colors.txt,status_bar_title_color) or something. It seems to be a lot of work to add nested theme tags like your example, I tried it before as a possible route when making the quickscreen tags, but it was far easier to create new tags.
Another thought is it would be nice if the Theme engine was such that the 'settings/themes/colours' option would allow you to pick a "secondary colour" (and perhaps even a "tertiary colour") as well as the "foreground" "background" and "selector bar" colours. There is a "line separator colour" setting, but if I ever knew what that does I've since forgotten it!
[Edit] experimenting with it, it seems it affects the separator between entries in the menus, if you set that to more than the default zero size in the appropriate settings menu.
Themes could then just make use of those user-chosen colour settings (in addition to setting via a config file) for variants like these, allowing them to be changed via the colour settings menu.
The big issue with using the settings colours currently is that most of them aren't exposed to the theme engine. For example, if you're using the themed lists feature you can't support the user's desired selector bar colour. The one pro I can see to an approach like this is that it would be more accessible to users using the screen reader, the setting entries could also be translated. But this would be limited still, I think a stylesheet approach would be better positioned to reduce the duplicates on the theme site (especially light and dark modes which could be stylesheets for a single theme instead of multiple versions)
99
User Interface and Voice / Re: A shortcut that requires a name
« Last post by iPodVT on June 05, 2025, 11:30:27 AM »[shortcut]
type: time
data: sleep 1
name: Sleep in 1 Minute
icon: -1
talkclip:
If anyone is wondering why I would use a 1 minute sleep timer, it's to expedite the investigation of sleep and/or shutdown related issues.
100
Theming and Appearance Customization / Re: themes with font support for both arabic and english other than stock?
« Last post by speachy on June 05, 2025, 09:31:06 AM »I've also been thinking about other ways to improve character coverage without having to make every font cover everything. This could come in the form of (for a given font size) one or more "fallback" fonts when the primary/selected font comes up short.
Anyway.
Anyway.