Given the default picker isn't great, I saw a welcome addition to v13
Every color now has a name. Named colors can be used in places like the status bar instead of a fixed RGB value. Use the right-click menu to get it.
But when I right-click within "Directory Opus Colors" on a color within color picker or anywhere else, I don't see any way to assign names to colors.
Ok, maybe this is applicable only to the status bars, I edit it, right click on <#008800> in {h!} <#008800><b>{hse}</b></#> {h!}, and also don't see anything
Would you please share an example on how to use named colors? Let's say I want to name #000000PureBlack and only use that name everywhere, what do I do?
I've added another post on what's wrong with it on a fundamental color-related level, but in this context the issue is the inability to save colors for reuse.
Let's say I've found a nice color in some theme I want to copy&paste, so I do that, and what if I later want to apply the same color to another element? Without saved names I'd have to remember where I originally applied it to, go there to copy, then save it in a newer element, which is very cumbersome.
I know there are some boxes in the current color picker where you could apply/save custom colors to, but my experience with these color pickers is that these are often reset, so I never use them. Besides, they have no names, and there are too few of them, so you can't really save a bunch of shades to live-pick from, it'd be easier to save rgbs in a text file and copy&paste from it
Being able to define a list of custom named colors would be nice, I guess.
But probably as something separate to the color picker, since it would have to interact with dark mode and themes, while the color picker may be used to store colors you want to use across themes/modes.
Which then has the problem of what to do if you use custom named colors and then load a theme which doesn’t have them.
It’d also require being able to tie one color to another (i.e. indirection), else it would be of limited use and colors could get out of sync with what they are meant to match. Which complicates things further…
We have been thinking about some ideas along those lines, but haven’t nailed down how it should work or if it would be something many people would use/understand. (Background images used to work this way, and people found it confusing. But it might make sense as an option instead of as the only way to do things.) It’s something we may revisit once the dust settles and we see how people are using colors/themes in the new version.
I’ve tended to just open a text editor and note down the colors I’m working with, if I want to use the same one in several places (e.g. when defining a theme). You can copy and paste colors to and from text format via the right-click menu on a color box (or the hamburger menu when the color picker is open for a color box).
Why noth both? If you want to tie colors to themes, you could have an explicit property of any given color name, where you have a .dark value and a .light value and a .universal value.
Or you could just do a simpler thing and define two LinkColorLight and LinkColorDark which would show in a list in the color picker while also be available in any other place where you need to set colors where you'd manually (or in a script based on the name variation) select the proper variant
So the them would use its own values or its own names within its own namespace? My named colors would still remain intact, the theme would just overwrite the names/values in specific items just like happens now
The simpler version of just being able to select a name is already an improvement
What if you want to select 1 shade out of 5 for the same element (e.g., a background)? You can't just ▼▲ and see the effects live. At least if DOpus config were text-based and tracked file changes you could quickly comment out a line and save and see the effect, but with ⎇⭾s and copy&pastes this is too much friction
The OP also said, "At least if DOpus config were text-based and tracked file changes you could quickly comment out a line and save and see the effect."
What’s wrong with it?