· None of the above quite fits
· None of these quite match
· Themes not respecting contents of Name file. If I change "Light" to "White" it becomes Unknown. If I create my own Theme, no matter what I enter into the Names file, it becomes Unknown.
· not relevant
Feels like this belongs more in Tinkering. Custom themes were never supported. And the theme names hasn’t been working for a long time (as you probably know).
But it used to, so I consider this a bug report.
Hi @Rugby,
To manage expectations here: since we have never officially declared or supported the ability to customize theme names via file modification, this falls into a bit of a gray area.
I cannot say for certain right now whether the development team will classify this as a bug or a feature request
I will pass the report along for review and will let you know the results here.
I appreciate it. But, when, it used to work (for years actually) and now it doesn’t. Personally I’d call that a bug, unless you planned to remove the ability. If the later, it would be good to know.
For years, I’d renamed the Light and Dark themes to Creamsicle and Night, respectively; as well as having my own listed, usually called “Orange”. Doing the same now just leaves me with a drop-down full of "unknown"s.
Hi @Rugby,
I hear you. When something works consistently for years and suddenly breaks, it definitely feels like a bug, regardless of whether it was officially documented or not.
I have some good news: I brought this up with the Product Team, and they agreed that it is worth investigating. They have asked me to file a formal report with R&D to see if this was an unintended regression that can be easily fixed.
I cannot promise a specific timeline or outcome just yet (as it depends on the complexity of the fix), but it is now officially in the queue for investigation. I will keep this thread updated as I hear back from the team.
Hi Vadim,
Thanks for the time on such a minor issue. I had found it weird because, the change meant something had been hard coded for some reason in the software.
Originally, the client read the “name” of the theme in the ‘name’ text file along with the ‘colors’ file in the specific theme folder. For example, the Light theme is actually in under a folder called “Creamsicle”. If you go and change the name in the text field, previously, it would display whatever text you entered, now, it will be displayed as Unknown.
This means that some routine is checking/validating an expected name vs the actual data in the name file. However, there is no limit to calling your new themes either Light or Dark. I can, for example, call my Orange theme “Dark”, and there would be 2 Darks in the Theme select drop down.
I find it weird, because, hard coding is more work than just reading the value from a file. Originally, there were going to be more themes, as I remember from conversations with the guys back then. Which meant that leaving the values to be read from the ‘name’ files, made sense.
Hey @Rugby
Thanks for the additionall information, we have added this info to the investigation ticket. The ticket has been submitted for developer review, meaning that this may take some time to be reviewed.
There aren’t any additional details needed at this time, so we will go ahead and close the thread for the time being, and if any other questions arise after the developers have reviewed the case, we will re-open the thread and reach out once more.
Thanks again for your report, and thank you in advance for your patience as the ticket progresses through the development queue for review.