On this page
NoteThis page contains release notes for GroupDocs.Annotation for .NET 18.1
Below is the list of most notable changes in release of GroupDocs.Annotation for .NET 18.1:
- Improved Replacement annotation for text in different paragraphs
- Fixed import text field for Diagram documents
- Fixed bug with import text annotations from pdf
- Fixed resizing image when user pass width and height
- Fixed creating of Arrow annotation for Diagrams
- Fixed issue with wrong distance structure after export in diagram
- Fixed issue with wrong polyline structure after export in diagram
|ANNOTATIONNET-583||Add text redaction annotation in Slides||New Feature|
|ANNOTATIONNET-582||Add point with text for text annotation||Improvement|
|ANNOTATIONNET-573||Improve export of text annotations in Slides||Improvement|
|ANNOTATIONNET-570||Improve annotation export for big font sizes for Slides||Improvement|
|ANNOTATIONNET-591||Fix Point annotation in Slides||Bug|
|ANNOTATIONNET-589||Fix opacity value for import in Diagrams||Bug|
|ANNOTATIONNET-584||Bug with import text field for diagram||Bug|
|ANNOTATIONNET-581||Arrow annotation doesn’t create for diagrams||Bug|
|ANNOTATIONNET-578||Fix Slides bug with coordinates of paragraph and portion||Bug|
|ANNOTATIONNET-577||Words:Fixed cleanup for text redaction annotation||Bug|
|ANNOTATIONNET-574||Bug with import text annotations from pdf||Bug|
|ANNOTATIONNET-572||Wrong distance structure after export in diagram||Bug|
|ANNOTATIONNET-571||Wrong polyline structure after export in diagram||Bug|
NoteThis section lists public API changes that were introduced in GroupDocs.Annotation for .NET 18.1. It includes not only new and obsoleted public methods, but also a description of any changes in the behavior behind the scenes in GroupDocs.Annotation which may affect existing code. Any behavior introduced that could be seen as a regression and modifies existing behavior is especially important and is documented here.
Was this page helpful?
Any additional feedback you'd like to share with us?
Please tell us how we can improve this page.
Thank you for your feedback!
We value your opinion. Your feedback will help us improve our documentation.