Bug 101724 - FORMATTING: Named colour styles
Summary: FORMATTING: Named colour styles
Status: RESOLVED DUPLICATE of bug 90497
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.1.4.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-25 09:59 UTC by imperativejonas
Modified: 2016-08-26 06:53 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description imperativejonas 2016-08-25 09:59:48 UTC
1. Use one of the colours in a palette for some styling on a few objects.
2. Change the values of that same colour in Tools>Options>Colours.
3. Click OK.
4. The styled objects keep their original colour but with the new name "User".

When I used several instances of the same named colour, I suspected to be able to change the values of that same colour and thereby change all instances. Something like colour styles.

I don't know if this is a bug report or a feature request.
Comment 1 imperativejonas 2016-08-25 14:19:37 UTC
OK! This seems to be a feature request.
Comment 2 Heiko Tietze 2016-08-26 06:53:21 UTC
The handling of user colors is being overhauled completely. You will have the opportunity to add colors to a special user palette and the access to palettes is possible from all pickers. That makes the Tools>Options>Colors setting obsolete. Much more improvements have been done, including the proper function of the recent colors. Not all features are committed yet but you may try a nightly build [1] to get an impression.

If you talk about styles you may have something in mind like document themes (bug 90497, will make this one a duplicate). That's work in progress, unfortunately with no schedule when it will be finished, as far as I know.

[1] https://www.libreoffice.org/download/pre-releases/

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