Copy link to clipboard
Copied
When using AddAnnotations API, the Undo icon appears.. but I'm loading annotations in from my servers database...
2. Undo/Redo
When I save the comments my server and reload them on a different computer, the "undo/redo" buttons appear immediately, and I can undo all the previous comments added from other users. Is there any way of blocking this?
Why are you able to undo annotations that werent inserted from the user? The undo button appearing is incredibly confusing for users who never added any annotations. What is there for them to undo??
Why is there two methods for AddAnnotations and AddAnnotationsInPdf also?
Copy link to clipboard
Copied
Copy link to clipboard
Copied
I'm adding a bug report for Undo showing up after annotations are added via API.
Copy link to clipboard
Copied
@Raymond Camden any update on when this will be prioritized and deployed to production?
Copy link to clipboard
Copied
Nope.
Copy link to clipboard
Copied
Additionally, it doesn't make sense that any annotations added by annotationManager.addAnnotations get emitted as
Copy link to clipboard
Copied
In regards to the event firing: Honestly I don't agree. If I tell the system to let me know when an annotation is added, no matter what the source. In the end, I'd rather the code always run and use code to programatically ignore when necessary. In this case (and I haven't looked at the code in an annotation object in a while), I'd imagine you could look at the timestamp.
Copy link to clipboard
Copied
I think that in a lot of cases where you are managing storing of the PDF annotations and updating using your own system, you don't actually want the undo/redo feature at all. For example, it is quite difficult to safely handle the cases where a user deletes another user's comment and then undoes this delete.
I would love an option that allows it to be disabled entirely, or disabled by default when