Skip to main content
Participating Frequently
October 24, 2021
Question

How to ignore save handling for annotation that are added programmatically?

  • October 24, 2021
  • 1 reply
  • 335 views

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.

This topic has been closed for replies.

1 reply

ahmed2mAuthor
Participating Frequently
October 25, 2021

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), then includePDFAnnotations is ignored.

2. If annotations APIs are enabled (enableAnnotationAPIs: true) and includePDFAnnotations: 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, no Save button appears in the top bar.

3. If both enableAnnotationAPIs and includePDFAnnotations are true, 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.