Description: Column-and-line ("combo" in MSO terminology) charts appear to be rendered in the order in which their constituent sub-charts appear in the OOXML. This doesn't cause a problem with LO-generated charts (since they are output with column first, line second, as generally desired), it can result in undesirable rendering of MSO-generated charts where (thin) lines are obscured by (wide) columns. Probably the best approach is to mimic MSO and order the rendering by type, rather than order in the OOXML. Steps to Reproduce: 1. Create column + line combo chart in MSO 2. Save and view in LO Actual Results: Line chart is rendered first, column chart rendered second, potentially obscuring significant portions of the line Expected Results: The line is rendered above the column chart, to make it more visible Reproducible: Always User Profile Reset: No Additional Info: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 69084d8e279dd42355bead9378e5a01c7bec036b CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Created attachment 191784 [details] Showing rendering of MSO-created and LO-created combos
I noticed you assigned yourself, do you plan to work on a fix?
Yes, I'm working on a fix. This is part of expanding support for combo charts more generally in LO.
Ok let's put this one to ASSIGNED then.
Proposed fix submitted here: https://gerrit.libreoffice.org/c/core/+/161797
Kurt Nordback committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/ca3112f38ea67d3cff1c9784adcc30ffcb200a0a tdf#159043: combo chart render order isn't right It will be available in 24.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Can this be closed as fixed?
I believe so, but I'm not sure if I'm allowed to make that change to the bug.
(In reply to kurt.nordback@protonmail.com from comment #8) > I believe so, but I'm not sure if I'm allowed to make that change to the bug. Fixing developers are the primary ones marking reports as resolved fixed.
Ah, okay. Still learning the processes.