Details
Description
When saving a document the isChanged() method does not reflect the fact that the document has been saved since the last change.
Procedure:
- start ICEpdf Viewer 5.0.4
- open a PDF document
- create a (random) annotation
- save the document
- close ICEpdf Viewer
Then you'll be prompted to save the changes before saving. This is not a behaviour consistent with common practice - if there are no changes since the last save I'll expect the viewer to simply close down!
It would be nice if the changes collection is updated automatically when saving the document but we also have implemented other save routines (Save, Save As, AutoSave/Backup, Export locked PDF etc) and would hence also like to be able to clear the changes collection from outside the StateManager() (See suggested solution in the workaround)
Procedure:
- start ICEpdf Viewer 5.0.4
- open a PDF document
- create a (random) annotation
- save the document
- close ICEpdf Viewer
Then you'll be prompted to save the changes before saving. This is not a behaviour consistent with common practice - if there are no changes since the last save I'll expect the viewer to simply close down!
It would be nice if the changes collection is updated automatically when saving the document but we also have implemented other save routines (Save, Save As, AutoSave/Backup, Export locked PDF etc) and would hence also like to be able to clear the changes collection from outside the StateManager() (See suggested solution in the workaround)
I've taken a look at this issue the clearing the StateManager after save is currently an issue as we don't reopen the written file and any subsequent saves will effectively trump any previous state data
Pushing out to 5.3 as we are hoping to write full write support to the original file with the option to do the update without an incremental update.