https://bugs.documentfoundation.org/show_bug.cgi?id=161072
--- Comment #2 from Caolán McNamara <[email protected]> --- It's possible that setting the color we want to use for the preview text via OutputDevice::SetTextColor instead of using Font::SetColor on the specific font, brings what the dialog does closer to the code paths that work better with this. Not sure if that would completely work, but it might help at least. We end up drawing these previews in SvxFontPrevWindow::Paint and we already explicitly pass down mxTextLineColor and mxOverlineColor for example, so an additional case there that does rRenderContext.SetTextColor with some new TextColor member, and then drop the various Font.SetColor calls in cui/source/tabpages/chardlg.cxx in favor of that alternative approach sounds useful and addresses the " // setting the color on the font is obsolete, the only remaining // valid use is for keeping backward compatibility with old MetaFiles const Color& GetColor() const; const Color& GetFillColor() const; " of include/vcl/font.hxx -- You are receiving this mail because: You are the assignee for the bug.
