You cannot rename a custom color.
To rename a color (just created) you'll have to delete it, then create it again with a different name. Unfortunately between these two steps the settings of the new color are lost.
It could be done much better!
The Custom color is written to user profile, i.e. registrymodifications.xcu, so trivial to directly edit with text editor without overhead of a GUI tool.
While improved GUI workflow for creation of custom colors is open as bug 124418 against the Color Picker widget. So modifications (including color name changes) while working in the custom or applied palettes would be simplified there.
IMHO => WFM and WONTFIX
(In reply to V Stuart Foote from comment #1)
> The Custom color is written to user profile, i.e. registrymodifications.xcu,
> so trivial to directly edit with text editor without overhead of a GUI tool.
That's no substitute for a UI; it's a "hack" at best.
> While improved GUI workflow for creation of custom colors is open as bug
> 124418 against the Color Picker widget. So modifications (including color
> name changes) while working in the custom or applied palettes would be
> simplified there.
I tried to get an impression what bug 124418 is about, but could find no reference to renaming a color.
(Also I'm unsure whether the "color picker" referred to can pick colors form LO objects only, or from any window. (The latter would be quite useful). In addition allowing an optional comment in addition to the name of a color would be useful)
> IMHO => WFM and WONTFIX
As stated on bug 127469, we should try to keep things simple and not implement functions for sake of maximizing features. But in this particular case I agree since users may do typos on creation and I would show the name dialog per context menu or on double-click.
See also bug 106551 about renaming palettes.
(In reply to Heiko Tietze from comment #3)
> (...). But in this particular
> case I agree since users may do typos on creation and I would show the name
> dialog per context menu or on double-click.
The other scenario is this: The name you would like to assign is being used already, and for consistency you want to rename the existing color (in addition to the new color).
Some arguments pro and some con. So let's keep the ticket.
OK, so question becomes how to rename. Efficient way would be to extend the color swatches when exposed in an active Palette tool instance. And from there provide some context menu actions against the swatch object:
1). add to Custom palette
2). name/rename color swatch (as held in Custom and/or Document palette)
3). adjust color (to launch 'Pick a Color' dialog)
The swatch attributes would be exposed from any active Palette tool instance, but 'rename' or 'adjust' would only apply when accessed from the Custom or Document palette.
(In reply to V Stuart Foote from comment #6)
Probably, too much overhead to extending attributes of all of a users' palettes--but extending the Recents and the Custom swatches as held in profile, along with the current Document colors would make for good work flows.
This is a duplicate of bug 106551 because both are about renaming colors in the custom color palette within the color area tab.
*** This bug has been marked as a duplicate of bug 106551 ***