Control the Export of Hidden Visio Pages and Retrieve Visio File Type using Aspose.Diagram for .NET 6.3.0

Share on FacebookTweet about this on TwitterShare on LinkedIn

Aspose.Diagram for .NET logoWe’re pleased to announce that the new version 6.3.0 of Aspose.Diagram for .NET API is now live. This new version brings a number of new features, enhancements and bug fixes. This version gives access to the developers to control the export of Hidden Visio pages in output files. Developers may also detect the Visio file type by its content and export diagrams with Arabic and Hebrew text. All this is achievable with Aspose.Diagram API.

Include or Exclude Hidden Pages of Visio on Saving to SVG, XPS, Image, HTML and PDF

Using Aspose.Diagram API, developers may hide the page of a Visio diagram through the cell UIVisibility in the page ShapeSheet yet they were not able to exclude the hidden pages on saving to output files. This version gives more access to the developers to make the decision whether they need to export the hidden Visio pages or not. The check of hiding the Visio pages is implemented for the output SVG, XPS, Image, HTML and PDF formats. This help topic shows how developers can include or exclude hidden pages of Visio in output files: Control the Export of Hidden Visio Pages on Saving

Detect the Type of Visio File

Developers may come across the scenario to automate the identification of file type by its content. Using Aspose.Diagram API, they can now figure out how to distinguish the Visio file type before any other manipulation. Thus, they can also make groups of Visio files to execute in their applications. This help topic shows how developers can detect the Visio file format: Detect the Format of Visio File

Improved Hebrew and Arabic Text Rendering

Aspose.Diagram API has provided support of reading and writing RTL (right to left) languages, such as Hebrew and Arabic. In this latest version, we have enhanced its export feature to place and render text in the same way as available in the input Visio diagram. We have fixed the problem of incorrect text direction as well as combining letters to form words in Arabic and Hebrew. We would really like to hear back from our users with their experiences in that area.

This new version also addresses the issues of losing textual style of the shapes, partial rendering of the text, missing shapes, wrong position of the shape and error messages while reading or writing diagrams. All this also improves the performance of Aspose.Diagram API. Please check a list of the resolved defects:

  • Fixed: VSD to PDF export – the table cell’s text is partially invisible.

  • Fixed: VDX to PDF export – the text of various shapes is misplaced.

  • Fixed: VSD to SVG export is missing some Visio shapes.

  • Fixed: VSD to SVG export is not applying the inner white color of shapes.

  • Fixed: Open and save routine of VSDX has changed the text into dummy characters.

  • Fixed: Open and save routine of VSDX has changed the dotted line shaper.

  • Fixed: VSD to PDF export – the text items are misplaced.

  • Fixed: VSD to VDX export is throwing the Master element error.

Public API Changes

The following API changes in the new version are also worth noting:

  • FileFormatUtil and FileFormatInfo classes are added.

  • DetectFileFormat method is added to the FileFormatUtil Class.

  • FileFormatType property is added to the FileFormatInfo Class.

  • LoadFormat property is added to the FileFormatInfo Class.

  • ExportHiddenPage property is added in the SVGSaveOptions, XPSSaveOptions, ImageSaveOptions, HTMLSaveOptions and PdfSaveOptions classes.

Aspose.Diagram for .NET Resources

The following resources will help you work with Aspose.Diagram for .NET:

We hope you’ll enjoy this new release that saves time and efforts. The API is quite simple and developers can use it in application easily.