<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Button to delete a color from the palette inactive anymore" href="https://bugs.documentfoundation.org/show_bug.cgi?id=132799#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Button to delete a color from the palette inactive anymore" href="https://bugs.documentfoundation.org/show_bug.cgi?id=132799">bug 132799</a> from <a class="email" href="mailto:frankaen@interia.pl" title="Piotr <frankaen@interia.pl>"> Piotr</a> <pre>(In reply to Julien Nabet from <a href="show_bug.cgi?id=132799#c1">comment #1</a>) > On pc Debian x86-64 with master sources updated today, I don't reproduce > this. > > I noticed that when creating a custom color, it was in > registrymodifications.xcu, a file which belongs to LO profile. > > For the test, could you rename your LO directory profile (see > <a href="https://wiki.documentfoundation.org/UserProfile#Windows">https://wiki.documentfoundation.org/UserProfile#Windows</a>) and give a new try? Hello, I did, and I can remove custom colors, but simply I was surprised these are not in .soc palettes in /config anymore, as we have custom company's palettes. So the problem now is when I use a custom .soc palette I cannot delete the color. Currently, custom colors are written in registrymodifications.xcu, and in values unrecognizable. What is needed then is to restore to ability to fully edit custom .soc palettes. Sorry, I was not clear about that, simply, I could not imagine someone would got the idea to remove this extremely clear and versatile way of writing down different, many custom palettes.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>