We have tested the scenarios in our environment and managed to observe the issues you have mentioned. We have logged them as following in our issue tracking system:
DIAGRAMNET-51658
DIAGRAMNET-51659
DIAGRAMNET-51660
We will surely let you know as soon as we make some significant progress towards their resolution. Please be patient and spare us little time.
You’re really great, these tickets 'DIAGRAMNET-51658, DIAGRAMNET-51659, DIAGRAMNET-51660’
are solved. Thanks for the updated version. We started to test some other files. If there is any issue we will let you know.
You’re awesome , these tickets **'DIAGRAMNET- 51664, DIAGRAMNET- 51665’
are solved. Thanks for the updated version. We started to test some other files. If there is any issue we will let you know.
The issue has been logged as DIAGRAMNET-51667 in our issue tracking system. We will further check this in details and keep you informed on its resolution status. Please spare us little time.
The issue has been logged as DIAGRAMNET-51671 in our issue tracking system. We will further check this in details and keep you informed on its resolution status. Please spare us little time.
The issues you have found earlier (filed as DIAGRAMNET-51664,DIAGRAMNET-51665,DIAGRAMNET-51667,DIAGRAMNET-51671) have been fixed in Aspose.Diagram for .NET 19.8.
You’re awesome , these tickets **’ DIAGRAMNET-51664,DIAGRAMNET-51665,DIAGRAMNET-51667,DIAGRAMNET-51671’
are solved. Thanks for the updated version. We started to test some other files. If there is any issue we will let you know.
We have logged this issue as DIAGRAMNET-51684 in our issue tracking system for further investigation. We will surely let you know in case we have additional updates regarding its resolution. Please spare us little time.
You’re awesome , the ticket **’ DIAGRAMNET-51684’
is solved. Thanks for the updated version. We started to test some other files. If there is any issue we will let you know.