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

Heiko Tietze <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #1 from Heiko Tietze <[email protected]> ---
(In reply to Thomas Lendo from comment #0)
> Suggestion 1:
> 
> Imported palettes should be handled like the custom palette with means to
> modify, remove and rename colors.

You would need to override the previous custom colors or to merge the two
lists. Both likely not wanted.

> Suggestion 2:
> 
> It should be possible to pick the custom color palette file and imported
> color palette files within a file manager in the user profile to copy, to
> edit it by hand or to rename it.

Don't get it, and it sounds strange.

The enhancement request is a clear WONTFIX for me. Color palettes are one mean
to handle a list of colors. You still have the document colors, the ordinary
color picker, own custom colors etc. 
There is no use case to make palette handling as easy as possible, and when we
add more options here it's feature-creep. Even the (IMHO more obvious) solution
#3, to define at the palette itself whether it is read-only or not, makes no
sense as it adds complexity (it's not the checkbox, or the like, that is
complex but all reasoning behind we do in this and other tickets that average
users are not aware of). People who want to go into detail should rather hack
the file.

> Where are custom and imported color palettes stored now...

Predefined palettes are placed at <LibO>/share/palette, the user palettes in
<user>/libreoffice/4/user/extensions/+, the custom palette is stored in
<user>/libreoffice/4/user/registrymodifications.xcu.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to