We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Control between NameU, Name and Comment for SVG tooltip

With Aspose Diagram Java, when a vsdx is exported to SVG the universal name (NameU) attribute of a shape is used to create the element for the shape’s element. This provides a tooltip when the SVG is viewed in a browser.

However, the initial shape name is stored as the NameU attribute in the Visio document and subsequently can’t be edited through the Visio UI. This means that when documents are edited by end-users and converted to SVG by Aspose Diagram, the tooltip on shapes can’t be updated.

Ideally, it would be possible to control whether a shape’s “Name” attribute or a shape’s Cell[N=“Comment”][V] values are used for the rather than just use the NameU attribute when saving as SVG.

To reproduce:

  1. Create a new Visio document
  2. Add a shape
  3. Select the new shape
  4. Go to Developer -> Shape Name
  5. Set the “Name” on the shape in the Shape Name dialog and press OK
  6. Save the Visio as vsdx
  7. Convert the file to SVG with Aspose diagram Java - the shape will be given the correct title
  8. Edit the vsdx document, repeating steps 3 to 6 and using a different shape name
  9. Re-convert the vsdx to SVG with Aspose diagram - the name of the shape in the title will not have updated
  10. Edit the vsdx
  11. Select the shape
  12. Select Insert -> ScreenTip
  13. Set a screen tip and save the file
  14. Re-convert the vsdx to SVG with Aspose diagram - the name of the shape in the title will not have updated to reflect the screen tip

Ideally, SVGSaveOptions would have some means of controlling where title was pulled from - ideally a means of ordering (e.g. use ScreenTip (if set), then Name (if set), then NameU). The default would be to use NameU to maintain existing behaviour.



Would you please let us know which platform you are using Aspose.Diagram in (.NET/Java)? We will log an investigation ticket accordingly and share the ID with you.


This is using Java.



Thanks for sharing requested information with us. We are working on this and will get back to you with feedback soon.