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

            Bug ID: 172466
           Summary: Remove rendermode (or add a label)
           Product: LibreOffice
           Version: 26.8.0.0 alpha0+ master
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Keywords: needsUXEval
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected],
                    [email protected], [email protected],
                    [email protected]
            Blocks: 83946

Created attachment 207451
  --> https://bugs.documentfoundation.org/attachment.cgi?id=207451&action=edit
Screenshot

With a couple of patches [1] a "rendermode" was introduced primarily for COOL
but also picked for LibreOffice, see [2] for details. What bothers me is the
use of hard-coded colors in [3] and the broken configuration in Tools > Options
> Writer > Changes, where deletions are still shown as strike-through. Plus,
using fix colors makes the identification of authors impossible (customizable
per appearance). Unlike COOL (AFAIK there is no options dialog) we can
configure TC right now to show as fix color instead of font attributes.

If we keep this we need to add a label - until now the command is listed as
uno:RenderMode in the customization. And we need documentation.

[1] https://gerrit.libreoffice.org/q/cool%2313988+branch:master
[2] https://github.com/CollaboraOnline/online/issues/13988

[3] 
SwFlyFrame::GetRedlineRenderModeFrame()

    if (eRedlineRenderMode == SwRedlineRenderMode::OmitInserts && IsDeleted())
    {
        oColor.emplace(COL_RED);
    }
    else if (eRedlineRenderMode == SwRedlineRenderMode::OmitDeletes &&
IsInserted())
    {
        oColor.emplace(COL_GREEN);
    }


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=83946
[Bug 83946] [META] Tracking changes issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to