Description: Attached Presentation shows Think-Cell chart with wrong values. Given values are replaced with dates. The PDF export is also wrong. Steps to Reproduce: 1. Open attached bug doc in LO6.3.1.2 2. Open attached bug doc in PowerPoi8nt 2016 3. Compare Actual Results: Attached Presentation shows Think-Cell chart with wrong values. Given values are replaced with dates. Expected Results: LO shows the same values as PowerPoint Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 154494 [details] bug doc 1 The bug doc for verification.
Chart values are ok, but X, Y and titles values are wrong Version: 6.4.0.0.alpha0+ Build ID: cc65651a0490383f1a833bb6215d8ec4272d8b5d CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded
Created attachment 154495 [details] comparison MSO 2010 and LibreOffice 6.4 Master
Also reproduced in Version: 4.3.0.0.alpha1+ Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
@Balazs, I thought you might be interested in this issue, at first glance it seems an easy fix for you, now that you are a chart expert ;-)
Created attachment 154513 [details] Textbox issue Thank you very much, Xisco. :) But as I see it, this is not a chart BUG, but a textbox issue. There's a chart, but there are text boxes around it. The problem occurs, without the chart too.
oh, good point, didn't check it when I triage the bug. thanks a lot!
Created attachment 156122 [details] The example file in current 6.4 master This seems to have gotten better (as the labels are imported correctly, but not as modifiable time/date fields) in: Version: 6.4.0.0.beta1+ (x64) Build ID: 1aa0e52f70e62022cffb499a609ac2def6245166 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; Locale: hu-HU (hu_HU); UI-Language: en-US Calc: threaded
Bibisecting with bibisect-win64-6.4 shows this is a result of the fix to bug #126324 *** This bug has been marked as a duplicate of bug 126324 ***