Visio file's tables not rendered when convert VSDX to PNG

Aspose.Diagram Product Family
1
Hello Ikram,

We have some more issues when converting to Visio to PNG.

When I convert the visio (VSDX) to PNG format using Aspose.Diagram.dll. The image files are successfully converted. But the converted image (PNG) quality is poor when compared with original visio file (VSDX). Some of the visio files has tables that are not rendered in PNG image. Here I have attached a document (issues) and the conversion sample.

Please suggest for this problems also.

Thanks.,
Rengarajan.
2
Hi Rengarajan,

Thank you for your inquiry.

Your inquiry is related to Aspose.Diagram. I have forwarded your inquiry to the appropriate forum where my colleague from Aspose.Diagram support team will update you accordingly.

3

Hi Rengarajan,


Thank you for contacting support. Please attach your word document again in this forum thread because we can’t download it. Please also provide your source Visio diagrams for testing purposes. It’ll help us to be more specific.

4

Hi Imran,

Thanks for your reply. Here I attached input visio files and output png files. Find the attachment.

Please suggest for this problems.

5
Hi Rengarajan,

Thank you for sharing problematic diagrams. You're using an evaluation version of Aspose.Diagram API. We recommend our clients get a 30 day temporary license for testing purposes. Please refer to the following help topic: Get a Temporary License

We managed to replicate the issues as below:

File Name: Dialog - 2.vsdx
DIAGRAMNET-50884: A table is missing on converting a VSDX to PNG

File Name: Dialog - 3.vsdx
DIAGRAMNET-50885: A table is missing on converting a VSDX to PNG

File Name: Dialog - 4.vsdx
DIAGRAMNET-50886: A table is missing on converting a VSDX to PNG

File Name: Dialog - 6.vsdx
DIAGRAMNET-50887: A table is missing on converting a VSDX to PNG

File Name: Dialog - 7.vsdx
DIAGRAMNET-50888: A table is missing on converting a VSDX to PNG

File Name: Dialog - 8.vsdx
DIAGRAMNET-50890: A table is missing on converting a VSDX to PNG

File Name: Dialog - 9.vsdx
DIAGRAMNET-50891: A table is missing on converting a VSDX to PNG

File Name: Dialog - 10.vsdx
DIAGRAMNET-50892: A table is missing on converting a VSDX to PNG

File Name: Dialog - 11.vsdx
DIAGRAMNET-50893: A table is missing on converting a VSDX to PNG

File Name: Dialog - 13.vsdx
DIAGRAMNET-50894: Tables are missing on converting a VSDX to PNG

File Name: Dialog - 14.vsdx
DIAGRAMNET-50895: Tables are missing on converting a VSDX to PNG

File Name: Dialog - 15.vsdx
DIAGRAMNET-50896: A table is missing on converting a VSDX to PNG

File Name: Dialog - 16.vsdx
DIAGRAMNET-50897: Tables are missing on converting a VSDX to PNG

File Name: Dialog - 17.vsdx
DIAGRAMNET-50898: A table is missing on converting a VSDX to PNG

File Name: Dialog - 18.vsdx
DIAGRAMNET-50899: Tables are missing on converting a VSDX to PNG

File Name: Dialog - 19.vsdx
DIAGRAMNET-50900: A table is missing on converting a VSDX to PNG

File Name: Dialog - 21.vsdx
DIAGRAMNET-50901: A table is missing on converting a VSDX to PNG

File Name: Dialog - 23.vsdx
DIAGRAMNET-50902: A table is missing on converting a VSDX to PNG

File Name: Dialog - 24.vsdx
DIAGRAMNET-50903: Tables are missing on converting a VSDX to PNG

File Name: Dialog - 25.vsdx
DIAGRAMNET-50904: Tables are missing on converting a VSDX to PNG

File Name: Dialog - 28.vsdx
DIAGRAMNET-50905: A table is missing on converting a VSDX to PNG

File Name: Dialog - 30.vsdx
DIAGRAMNET-50906: Tables are missing on converting a VSDX to PNG

File Name: Dialog - 32.vsdx
DIAGRAMNET-50907: A table is missing on converting a VSDX to PNG

File Name: Dialog - 33.vsdx
DIAGRAMNET-50908: A table is missing on converting a VSDX to PNG

File Name: Dialog - 35.vsdx
DIAGRAMNET-50909: Icons are changed while converting a VSDX to PNG

File Name: Dialog - 36.vsdx
DIAGRAMNET-50910: A table is missing on converting a VSDX to PNG

File Name: Dialog - 38.vsdx
DIAGRAMNET-50911: A table is missing on converting a VSDX to PNG

File Name: Dialog - 39.vsdx
DIAGRAMNET-50912: Tables are missing on converting a VSDX to PNG

File Name: Dialog - 41.vsdx
DIAGRAMNET-50913: A table is missing on converting a VSDX to PNG

File Name: Dialog - 42.vsdx
DIAGRAMNET-50914: A table is missing on converting a VSDX to PNG

File Name: Dialog - 44.vsdx
DIAGRAMNET-50915: A table is missing on converting a VSDX to PNG

File Name: Dialog - 45.vsdx
DIAGRAMNET-50916: A table is missing on converting a VSDX to PNG

Your post has also been linked to these tickets. We'll keep you informed regarding any available updates. We're sorry for the inconvenience caused.

Please also elaborate a bit more about the image quality problem. Aspose.Diagram API mimics the behavior of Microsoft Office Visio. You can convert Visio diagrams using Microsoft Office Visio and then compare with Aspose outputs.

6

Hi Rengarajan,


Thank you for being patient. We have a good news for you that the ticket id DIAGRAMNET-50884 and DIAGRAMNET-50887 have now been resolved. If there is no issue in the QA phase, then their fixes will be incorporated in the next version 6.7.0 of Aspose.Diagram for .NET API. We’ll inform you via this forum thread as soon as the new release is published.

7

Hi Rengarajan,


Thank you for being patient. We have a good news for you that the ticket id DIAGRAMNET-50908, DIAGRAMNET-50909, DIAGRAMNET-50910 and DIAGRAMNET-50911 have now been resolved. If there is no issue in the QA phase, then their fixes will be incorporated in the next version 6.7.0 of Aspose.Diagram for .NET API. We’ll inform you via this forum thread as soon as the new release is published.

8

Hi Rengarajan,


Thank you for being patient. We have a good news for you that the ticket id DIAGRAMNET-50885, DIAGRAMNET-50886, DIAGRAMNET-50888, DIAGRAMNET-50890, DIAGRAMNET-50891, DIAGRAMNET-50892, DIAGRAMNET-50893, DIAGRAMNET-50894, DIAGRAMNET-50895, DIAGRAMNET-50896, DIAGRAMNET-50897, DIAGRAMNET-50898, DIAGRAMNET-50899, DIAGRAMNET-50900, DIAGRAMNET-50901, DIAGRAMNET-50902, DIAGRAMNET-50903, DIAGRAMNET-50904, DIAGRAMNET-50905, DIAGRAMNET-50906, DIAGRAMNET-50907, DIAGRAMNET-50912, DIAGRAMNET-50913, DIAGRAMNET-50914, DIAGRAMNET-50915 and DIAGRAMNET-50916 have now been resolved. If there is no issue in the QA phase, then their fixes will be incorporated in the next version 6.7.0 of Aspose.Diagram for .NET API. We’ll inform you via this forum thread as soon as the new release is published.

9

Hi Imran rafique,


Thanks for your reply, we are expecting your new version.
Sorry for the late reply.

Thanks
Rengarajan.
10

Hi Rengarajan,


Thank you for being patient. Our product team has plans to release the next version 6.7.0 in next week. We’ll notify you in this forum thread once the new version becomes available for the public use.

11

Hi Rengarajan,


Thank you for being patient. In reference to the ticket ids DIAGRAMNET-50884, DIAGRAMNET-50885, DIAGRAMNET-50886, DIAGRAMNET-50887, DIAGRAMNET-50888, DIAGRAMNET-50890, DIAGRAMNET-50891, DIAGRAMNET-50892, DIAGRAMNET-50893, DIAGRAMNET-50894, DIAGRAMNET-50895, DIAGRAMNET-50896, DIAGRAMNET-50897, DIAGRAMNET-50898, DIAGRAMNET-50899, DIAGRAMNET-50900, DIAGRAMNET-50901, DIAGRAMNET-50902, DIAGRAMNET-50903, DIAGRAMNET-50904, DIAGRAMNET-50905, DIAGRAMNET-50906, DIAGRAMNET-50907, DIAGRAMNET-50908, DIAGRAMNET-50909, DIAGRAMNET-50910, DIAGRAMNET-50911, DIAGRAMNET-50912, DIAGRAMNET-50913, DIAGRAMNET-50914, DIAGRAMNET-50915 and DIAGRAMNET-50916, please download and use the latest Hotfix version: Aspose.Diagram for .NET 6.6.1.0. Please also let us know how that goes on your side.

12
Hi Imran Rafique,

Thanks for your support, i will check and update the status.


Thanks
Rengarajan
13

Hi Rengarajan,


Sure, please take your time and let us know about your precious feedback. We’ll be happy to help you in using Aspose APIs in your project applications.

14
Hi Imran Rafique,
Thanks for your assistance and your new Aspose.Diagram for .NET 6.6.1.0. version.

Now we can see the lot of issues solved. But we have some issues in this new version.

Please suggest for this issues also.

Here i attached the Input, Output and BugList files


Thanks and Regards
Rengarajan N
15

Hi Rengarajan,


Thank you for the details. We noticed that each of your output PNG file has an evaluation watermark. It means you have not applied a valid Aspose license. To apply a valid license, please refer to the following help section: License Aspose.Diagram for .NET

In reference to the listed bugs, we have checked your Visio diagram (Dialog - 7.vsdx). The left and top borders of the table are visible in the output PNG after applying the license. Please apply license, regenerate all your PNGs, and then list down each filename with its problems.

We’re looking forward to help you.

16
Hi Imran Rafique,

Thank you for your information, i will check and update the status.


Thanks
Rengarajan
17

Hi Rengarajan,


Sure, please take your time and let us know about your findings. We’ll be happy to help you in using Aspose.Diagram API in your project applications.

18

Hi Imran Rafique,


I convert the file from VSDX to PNG with Aspose.Diagram
for .NET 6.6.0 (DLLs Only), already I have Aspose license. But it’s always shows
evaluation watermark in output file.

I attached the document with detail, Please see my attachment and give a solution

Thanks
Rengarajan.N

<o:p></o:p>

19

Hi Rengarajan,


Thank you for the inquiry. Please send us your Aspose license file for the testing purposes via an email as narrated there: Send Your License File to an Aspose Staff Member. We’ll investigate and reply you appropriately.

20

The issues you have found earlier (filed as DIAGRAMNET-50884;DIAGRAMNET-50885;DIAGRAMNET-50886;DIAGRAMNET-50887;DIAGRAMNET-50888;DIAGRAMNET-50890;DIAGRAMNET-50891;DIAGRAMNET-50892;DIAGRAMNET-50893;DIAGRAMNET-50896;DIAGRAMNET-50898;DIAGRAMNET-50900;DIAGRAMNET-50901;DIAGRAMNET-50902;DIAGRAMNET-50905;DIAGRAMNET-50907;DIAGRAMNET-50908;DIAGRAMNET-50910;DIAGRAMNET-50911;DIAGRAMNET-50913;DIAGRAMNET-50914;DIAGRAMNET-50915;DIAGRAMNET-50916;DIAGRAMNET-50894;DIAGRAMNET-50895;DIAGRAMNET-50897;DIAGRAMNET-50899;DIAGRAMNET-50903;DIAGRAMNET-50904;DIAGRAMNET-50906;DIAGRAMNET-50912;DIAGRAMNET-50909) have been fixed in Aspose.Diagram for .NET 6.7.0.

This message was posted using Notification2Forum from Downloads module by Aspose Notifier.