Bug 129811

Summary: Color picker control should have custom palette management buttons
Product: LibreOffice Reporter: Mike Kaganski <mikekaganski>
Component: LibreOfficeAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: enhancement CC: vsfoote
Priority: medium Keywords: needsUXEval
Version: unspecified   
Hardware: All   
OS: All   
See Also: https://bugs.documentfoundation.org/show_bug.cgi?id=127469
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: Area dialog vs color picker drop-down

Description Mike Kaganski 2020-01-05 15:22:18 UTC 
Created attachment 156946 [details]
Area dialog vs color picker drop-down

Currently the only way to create a custom palette is from Area dialog. But area dialog is not intuitive place to look for this functionality; most users meet colors more often using color picker drop-down. The drop-down is used on Format toolbar;  The drop-down resembles left part of the Area dialog; in Character properties (font color selection), in Line properties, border properties, etc.

Additionally, it's required to activate the Area dialog's Color button to access the custom palette controls. Users are confused finding it [1].

The proposal is to add the two buttons (Add/Delete custom palettes) into the picker. It has small enough height to accommodate the buttons (which additionally could be made small buttons with + and - to the right of the palette selector), and that would make this feature accessible.

[1] https://ask.libreoffice.org/en/question/223880
Comment 1 V Stuart Foote 2020-01-05 17:06:25 UTC 
@Mike, functionally seems a dupe to bug 106551 (or its dupe bug 127468)?  Especially as there is only one 'Custom' palette of color swatches as recorded to user profile.

Externally prepared palettes can of course be added by placing the .SOC/.SOG/.ASE palette into the share/palette directory.
Comment 2 V Stuart Foote 2020-01-05 17:12:53 UTC 
Actually maybe more directly a dupe of bug 124418
Comment 3 Mike Kaganski 2020-01-05 17:16:22 UTC 

*** This bug has been marked as a duplicate of bug 124418 ***