You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Everything is fine, if we write a workbook we have created. The issue stems from incorrect vml numbering if a sheet contains no vml reference. In theory it should be a simple workbook with two empty sheets and a comment on the second.
The vml file will be vmlDrawing1.xml if written from Excel and vmlDrawing2.xml if written from us. Because we wrongfully assume that every sheet has a matching vml file if one is available. Unfortunately that's not true. In this case we have updated all but the worksheet reference to point to vml2. In the worksheet references we still point to vml1 and the XLSX output will not find the files and excel will repair the workbook by removing all vml references.
To solve this, we have to change the vml reordering. I'm not sure how complicated this is going to be. Either we have created a very complicated nonsense or ...
Updated with example: we see two sheets, assume two vmlDrawings. Yet the reference remains pointing at vmlDrawing1.xml. This should be fixed to match what Excel creates. Otherwise I fear that in some more messed up file, we will break due to some not updated reference order.
This should impact everything that interferes with vmlDrawings or drawings in general. I kinda was under the impression that we had already fixed this with this strange file where the custom drawing was interfering with the reference counter.
Everything is fine, if we write a workbook we have created. The issue stems from incorrect vml numbering if a sheet contains no vml reference. In theory it should be a simple workbook with two empty sheets and a comment on the second.
The vml file will be
vmlDrawing1.xml
if written from Excel andvmlDrawing2.xml
if written from us. Because we wrongfully assume that every sheet has a matching vml file if one is available. Unfortunately that's not true. In this case we have updated all but the worksheet reference to point tovml2
. In the worksheet references we still point tovml1
and the XLSX output will not find the files and excel will repair the workbook by removing all vml references.To solve this, we have to change the vml reordering. I'm not sure how complicated this is going to be. Either we have created a very complicated nonsense or ...
Updated with example: we see two sheets, assume two vmlDrawings. Yet the reference remains pointing at
vmlDrawing1.xml
. This should be fixed to match what Excel creates. Otherwise I fear that in some more messed up file, we will break due to some not updated reference order.This should impact everything that interferes with
vmlDrawings
ordrawings
in general. I kinda was under the impression that we had already fixed this with this strange file where the custom drawing was interfering with the reference counter.The text was updated successfully, but these errors were encountered: