https://bugs.documentfoundation.org/show_bug.cgi?id=165889

            Bug ID: 165889
           Summary: Outline view should respect font color
           Product: LibreOffice
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Impress
          Assignee: [email protected]
          Reporter: [email protected]
            Blocks: 125823

The outline view shows the slide content with minimal capabilities to view and
edit. The paragraph attributes are respected as well as the character
background. But not the font color nor other attributes. The font color is some
highly relevant attribute though as it is being calculated against the
background - and if the user inverts the text ie. black background, white font
- it wont be visible anymore in the outline view.

Furthermore, the font color is always black. If the document color is set to
some dark value the view is broken. The band-aid from bug 165803 may help for
now but actually it would be nicer to have the app background on the outline
view (besides customization).

Tried something at

OutlineView::onUpdateStyleSettings() GetColorValue( svtools::DOCCOLOR ).nColor
-> APPBACKGROUND

and at the PaintingFirstLineHdl -> aColor( aColorConfig.GetColorValue(
svtools::APPBACKGROUND ).nColor.IsDark() ? COL_WHITE : COL_BLACK );
aNewFont.SetColor( aColor ); plus pInfo->mpOutDev->SetTextColor ( aColor );

but the issue needs to be solved in the SdOutliner or some other close closer
to the EditEngine maybe. 

In other words: Accepting the paragraph attributes in particular the background
color in OutlineView::UpdateParagraph() requires to respect the font color (and
use white/black in case of auto depending on the background).


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=125823
[Bug 125823] [META] Personalization (LibreOffice Themes) bugs and Improvements
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to