As the title says. If I on pdf initialization, added a new annotation (loaded from json saved before) via the annotationManager this will trigger the save button and will show Edited -- (Save button) in the header.
I was wondering if there's a way to avoid this behaivor and just show the annotation, without disabling the user ability to add/remove new annotations, and showing the save button only on user actions/events.
I found the below section below in the documentation, is there a way to make `includePDFAnnotations` only listen to user invoked actions not programmatically calling annotationManager.addAnnotations(x)
1. If the annotation APIs are not enabled (enableAnnotationAPIs:false), thenincludePDFAnnotationsis ignored.
2. If annotations APIs are enabled (enableAnnotationAPIs:true) andincludePDFAnnotations:false, then:
The PDF Embed API does not display existing annotations, but will display new ones.
Any annotation added or updated either from the UI or API is not saved to the PDF buffer; therefore, noSavebutton appears in the top bar.
3. If bothenableAnnotationAPIsandincludePDFAnnotationsaretrue, then:
Any existing annotation the PDF Embed API supports is displayed and accessible through these APIs. Note that unsupported annotations appear in read-only mode and are not accessible to the APIs.
Any annotation added or updated from UI or API is saved to the PDF buffer, and the Save button is enabled when the PDF has unsaved changes.