[Libreoffice-bugs] [Bug 137735] FILESAVE: Chart defects when reopening : loss of backwards compatibility

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Mon Oct 26 12:22:00 UTC 2020


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

--- Comment #2 from matthewnote at yahoo.co.uk ---
Created attachment 166732
  --> https://bugs.documentfoundation.org/attachment.cgi?id=166732&action=edit
Screenshot; Comparing unzipped odf content.xml between Calc 5 and Calc 4

This (user) comment attempts to provide information about :
Which versions of Calc can restore a file with Chart Update defects using
File>open File>save (close file) File>open.
Which versions tested did not do this.

All versions of Calc 4,5,6,7,Fresh can cause Objects (charts) to fail to update
the scatter plots when their Data Series have changed.  To do this
deliberately, the Step by Step is at Bug 86321 Comment 78.  A file with several
sheets and three or four x,y scatter Charts on each sheet is given a new
inserted sheet (empty) between others.  Then (mostly) charts elsewhere fail to
update or change their x axes incorrectly (using any version of Calc 4,5,6,7). 
This provides a test file for this Bug Report.  

The fault is often (but not always) permanent when using Calc 4,6,7,Fresh.  
With Calc 5, the defect is the same, yet most versions 5 have a save or open
(or both) method/organisation that displays all charts working again.  Only
Calc 5 can do this every time.

Ubuntu parallel Calc Versions reactions to File, Open - Save - Close - Open
5.0.0.1  The test file opens with charts frozen. Save, close then re-opens with
charts  still frozen.  Repair/restore failed.
5.0.0.4  The test file opens with charts all working.  Save, close then
re-opens with charts frozen again.  Repair/restore half successful (the Open
works but not the Save).  [Note:Usually, with all Calc versions, moving the
Chart area a few pixels will cause a scatter plot to update to the real series'
values.  5.0.0.4 did not do this workaround when tested here.]
5.0.0.5  The test file opens with charts all working. To test more, the file is
deliberately broken using Insert>Sheet between two sheets that have charts. 
Bug 86321 expressed again, various charts frozen or with incorrect x-axes
format.  Save then re-opens the file with all charts working.  Earliest version
Repair/restore successful.
5.0.1.1  Same as 5.0.0.5  Repair/restore successful.
5.0.3.2  While working, editing or deliberately causing frozen charts, 5.0.3.2
is like 5.0.0.4;  moving the Chart area a few pixels did not do a workaround. 
However Save re-opens same as 5.0.0.5.  Repair/restore successful.
5.1.0.1, 5.1.6.2, 5.2.0.4, 5.3.6, 5.4.7 Repair/restore successful. 

All 6.0.0+, all versions up to 7.0.1.2 and Fresh.  Test file usually opens
defective.  More insertions of empty sheets usually causes more charts frozen
everywhere.  File Save Close Re-open usually does not repair the frozen charts. 

Exception A.  Sometimes a file generated on (for example Linux+ 6.3.5.2) with
defective redraw of Charts may Open with charts working on a different computer
(for example Windows+ 7.0.1.2).  Sent back to the source computer, the file may
also have charts working before Bug 86321 expresses again.

Exception B. Upgrading from Calc 6.3.5.2 (official Ubuntu 18.04 LTS companion)
to Calc 7.0.1.2 (using ppa outside the Ubuntu support): Calc did something
unique and unusual.  Unlike all versions Calc 4,6 the upgrade to 7 once (and
only once) generated ObjectReplacements for each every chart. Usually only Calc
5 always does this on Linux.  [The broken file was else than used here for
these Bug reports and is too large to attach]. File>Open showed all Charts
working immediately and they all still do for that file. Downgrading from Calc
7 and reinstalling official 6.3.5.2 then doing the upgrade process again to LO7
did not repair any other defective file.



Coincidental information:  this may not be the indicator of the File>Open and
File>Save File>close File>Open success of Calc 5 versions.  It's a coincidence
that Calc 4, Calc 6.0.0 and Calc 7 do not share this save behaviour.

Description of the attachment using QXmlEdit. 

The screenshot (right hand side in red) shows that the Calc 4 used to save a
defective charts file, wrote content.xml using draw:object
<table:table-row><table:table-cell><draw:frame><draw:object> Attributes:
draw:notify-on-update-of-ranges=roX09 . . . . . .

Calc 5 up to 5.4.7 changes the strategy.   The screenshot (left hand side in
green) shows that Calc 5 has opened the version 4 file, reads that Object 17,
updates the Chart correctly when data series cell values change.  Saving the
file, Calc 5 deletes the original Attribute (gone), then adds a completely new
element in content.xml one level up at draw:frame
<table:table-row><table:table-cell><draw:frame><loext:p> Attributes:
draw:notify-on-update-of-ranges=roX09 . . . . . .
Calc 5 also adds another completely new attribute into Object 17/content.xml
<style:style><style:chart:properties>Attributes:
loext:try-staggering-first="true"

Calc 6 and 7.  These versions remove the Calc 5 strategy (the entries are
deleted ) and saves with the same xml organisation as for version 4.   This is
deliberate or a regression?

Please note a hope. Even if Bug 86321 is fixed and Calc has a new Open/Save
method to fix this Bug, the ability to "refresh/reorganise/repair" a former
file is the reason for this Report.  I, personally can generate files with
6.3.5.2 and repair them daily with 5.4.7 because the Project doesn't use newer
functions.  Not always possible when working with Calc 7 and
statistics-double-exponential and so forth.

Test computer.  Ubuntu Bionic Beaver 18.04 using Parallel Versions of
LibreOffice, remembering to start early versions 5 with 
SAL_USE_VCLPLUGIN=gen ./soffice
(I find here that the ./soffice is usually in opt/libreoffice5.0/program or
5.1)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20201026/8445094d/attachment-0001.htm>


More information about the Libreoffice-bugs mailing list