After updating to the latest version 25.10, we faced the problem. The attached archive contains the .vsdx document. After converting .vsdx to .svg (C# language) two elements in the diagram were corrupted. These elements are getting gigantic in size. Would you have are look the attachment and fix the problem.
The conversion code looks simple, like this:
var option =
(Aspose.Diagram.Saving.SVGSaveOptions)Aspose.Diagram.Saving.SaveOptions.CreateSaveOptions(
SaveFileFormat.Svg);
option.PageIndex = 0;
diagram.Save(“InputFile.vsdx”, option);
I understand you’re facing issues with the conversion of a .vsdx file to .svg, where two elements in the diagram are becoming excessively large. This may be related to how certain elements are rendered during the conversion process.
To troubleshoot this, please consider the following steps:
Check Element Properties: Verify that the properties of the elements in the original .vsdx file are set correctly. Scaling issues can often arise from incorrect settings in the source file.
Update SVGSaveOptions: Experiment with different settings in the SVGSaveOptions. While the Scale property is not available in the current context, you can explore other options that may affect rendering.
Test with Different Pages: If your diagram contains multiple pages, try converting a different page to see if the issue persists. This can help determine whether the problem is with specific elements or the entire document.
Use a Different Format: If the issue continues, consider converting the .vsdx file to another format (such as PDF or PNG) first, and then to SVG. This approach can sometimes help preserve the layout and size of elements.
Here’s a modified version of your code that sets up the SVGSaveOptions:
var option = new Aspose.Diagram.Saving.SVGSaveOptions();
option.PageIndex = 0; // Specify the page to convert
diagram.Save("OutputFile.svg", option);
If the problem persists after trying these suggestions, please reach out to Aspose support with specific details about the elements that are affected, as they may provide more targeted assistance.
@krserg
Thanks for the template file and output svg.
We reproduced the problems you mentioned by converting your template VSDX file to SVG.
We found that the two arrows at the bottom were drawn incorrectly.
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): DIAGRAMNET-53824
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
The issues you have found earlier (filed as DIAGRAMNET-53824) have been fixed in this update. This message was posted using Bugs notification tool by philip.zhou