<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - wrong Bar color name in the Data bar dialog (#0000FF instead of Blue)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125288#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - wrong Bar color name in the Data bar dialog (#0000FF instead of Blue)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125288">bug 125288</a> from <a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> V Stuart Foote</a> <pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=125288#c2">comment #2</a>) And, the actual hard coded color set for maPositiveColor [1] is the color constant COL_LIGHTBLUE -- ( 0x00, 0x00, 0xFF ) [2] Option #1 -- Could define a different constant to pick up the blue from standard.soc Option #2 -- shift UI use of conditional formatting from standard.soc to tonal.soc, i.e. perform a palette change and pick up labeling from tonal.soc Option #3 -- Could edit the COL_LIGHTBLUE to match the standard.soc (broader potential impact across UI and in unit tests). IMHO Option #2 seems a better way to correct this--not clear how many unit tests would have to also be tweaked with Option #1, and Option #3 would be kind of invasive. =ref-= [1] <a href="https://opengrok.libreoffice.org/xref/core/sc/source/ui/condformat/condformatdlgentry.cxx?r=00ae441b#1107">https://opengrok.libreoffice.org/xref/core/sc/source/ui/condformat/condformatdlgentry.cxx?r=00ae441b#1107</a> [2] <a href="https://opengrok.libreoffice.org/xref/core/include/tools/color.hxx?r=d14d1341#282">https://opengrok.libreoffice.org/xref/core/include/tools/color.hxx?r=d14d1341#282</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>