Date: prev next · Thread: first prev next last
September 2019 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=127468

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Ulrich.Windl@rz.uni-regensb
                   |                            |urg.de

--- Comment #2 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> ---
(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

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.