I’ve reported a number of issues and some of these have now been outstanding for a number of months (these are listed below). Please can you give an update of the status of this work? We’re planning a major software release shortly and these problems will impact our customers if they’re not addressed.
Thanks, Andrew
DIAGRAMNET-51190 (Hyperlink in top right hand corner not displayed properly)
DIAGRAMNET-51194 and DIAGRAMNET-51198 (Shading on hyperlink button with up arrow in bottom left corner not displaying correctly)
DIAGRAMNET-51197 (Warning triangle is not rendered correctly (exclamation is too high))
@andrew.ridgeley,
We have logged an ETA request under the each ticket ID (DIAGRAMNET-51190, DIAGRAMNET-51194, DIAGRAMNET-51198 and DIAGRAMNET-51197). We will let you know once a significant progress has been made in this regard.
Best Regards,
Imran Rafique
@andrew.ridgeley,
Please find the latest updates as below:
DIAGRAMNET-51197 - Our product team has plans to fix this issue in the next couple of weeks.
DIAGRAMNET-51198 - Our product team has plans to fix this issue in the next month.
DIAGRAMNET-51194 - Our product team has plans to fix this issue in the next month.
DIAGRAMNET-51190 - It is a complex task and may take more time than usual. It is dependent on an internal feature. We cannot share ETA for now.
Best Regards,
Imran Rafique
Would it be possible for you to provide an update on timescales for these issues? I notice that the issues have not been fixed in the original timescale that you estimated.
We also have some more issues that have been reported and noted, so please could you provide an update on the progress of these as well? The issues are:
DIAGRAMNET-51233 (invisible text and mis-formed warning triangle)
DIAGRAMNET-51295 (low quality of SVG output)
DIAGRAMNET-51253 (incorrect colour of text and connectors in shapes)
If the issues cannot be resolved in the 17.8 release, we may consider escalating them to the priority support forum.
Regards,
Andrew
@andrew.ridgeley,
These ticket IDs are not resolved yet and pending for the analysis. In order to escalate them, kindly create a new thread in the priority forum and mentioned these ticket IDs in the post.
It has already been resolved in the previous version 17.6 of Aspose.Diagram for .NET API. Kindly download and try the latest version 17.7 of Aspose.Daigram for .NET API.
Best Regards,
Imran Rafique
Thanks for the update. I have re-tested the issue DIAGRAMNET-51253 with release 17.7 and can confirm that the issue is NOT fixed. We still have the original problem of the connectors not showing up.
Regards,
Andrew
Imran, over a month ago, this was the status. Do you have an update on these 3 issues?
@andrew.ridgeley,
We have re-evaluated your ticket ID DIAGRAMNET-51253 with the latest version 17.7, and can confirm you that it was about the incorrect color of the text and borders of shapes. The problem of the missing or incorrect color of the text has been fixed. We can find the problem of missing connecting lines and have logged tickets in our bug tracking system as below:
File Name: PUR.vsdm
DIAGRAMNET-51323: VSDM to SVG - all connecting lines are missing
DIAGRAMNET-51324: VSDM to SVG - incorrect border style and border color of various shapes
We have linked your post to these tickets and will keep you informed regarding any available updates. We are sorry for the inconvenience caused.
We are in communication with our product team and will let you know about the latest updates. We are sorry for the inconvenience caused.
@andrew.ridgeley,
In reference to the ticket ID DIAGRAMNET-51197, it is not resolved yet. Furthermore, our product team has plans to resolve and include its fix in the next version 17.8 of Aspose.Diagram for .NET API.
In reference to the ticket IDs DIAGRAMNET-51194 and DIAGRAMNET-51198, both these tickets are not resolved yet. These are the complex issues and may take more time than usual. Our product team has plans to resolve them in the 3rd quarter of year 2017.
Best Regards,
Imran Rafique
Thanks for the update. I can confirm that the text on shapes is now showing correctly. I’ll await your updates on the other 2 issues with this map.
Regards,
Andrew
@andrew.ridgeley,
Thank you for the confirmation. Sure, we will notify you once other 2 issues are resolved.
Best Regards,
Imran Rafique
@andrew.ridgeley,
The ticket IDs DIAGRAMNET-51323 and DIAGRAMNET-51324 have been resolved. If there is no issue in the quality assurance phase, then their fixes will be included in the next version 17.8 of Aspose.Diagram for .NET API. We will notify you once the next version is published.
Best Regards,
Imran Rafique
@andrew.ridgeley,
The ticket ID DIAGRAMNET-51295 has been resolved. If there is no issue in the quality assurance phase, then this fix will be included in the next version 17.8 of Aspose.Diagram for .NET API. We will notify you once the next version is published.
Best Regards,
Imran Rafique
@andrew.ridgeley,
The ticket ID DIAGRAMNET-51197 has been resolved. If there is no issue in the quality assurance phase, then this fix will be included in the next version 17.8 of Aspose.Diagram for .NET API. We will notify you once the next version is published.
Best Regards,
Imran Rafique
The issues you have found earlier (filed as DIAGRAMNET-51197) have been fixed in Aspose.Diagram for .NET 17.8. This message was posted using BugNotificationTool from Downloads module by imran.rafique
The issues you have found earlier (filed as DIAGRAMNET-51197) have been fixed in Aspose.Diagram for .NET 17.8. This message was posted using BugNotificationTool from Downloads module by imran.rafique
@andrew.ridgeley,
The ticket IDs DIAGRAMNET-51197 and DIAGRAMNET-51323 have been fixed. Please download and try the new version 17.8 of Aspose.Diagram for .NET API.
Best Regards,
Imran Rafique
@andrew.ridgeley,
The ticket ID DIAGRAMNET-51324 has been fixed. Please download and try the new version 17.8 of Aspose.Diagram for .NET API.
Best Regards,
Imran Rafique
The issues you have found earlier (filed as DIAGRAMNET-51198) have been fixed in Aspose.Diagram for .NET 20.1.