Bug #1981
RCP: X.X, Use Eclipse editor dirty mechanism to prompt for annotation save
Status: | New | Start date: | 01/02/2017 | ||
---|---|---|---|---|---|
Priority: | Normal | Due date: | |||
Assignee: | - | % Done: | 80% |
||
Category: | Annotation | Spent time: | - | ||
Target version: | TXM Democrat 3.0 |
Description
Currently the save annotation prompt dialog is called when the editor dispose event is raised. It works but we should use Eclipse save features to do it. (e.g. when the text editor Eclipse prompt a save message)
MD: use firePropertyChange(PROP_DIRTY);
History
#1 Updated by Matthieu Decorde over 6 years ago
- Subject changed from RCP: X.X, Use Eclipse auto-save job to save annotations to RCP: X.X, Use Eclipse editor dirty mechanism to prompt for annotation save
- Description updated (diff)
#2 Updated by Matthieu Decorde over 6 years ago
- % Done changed from 0 to 80
use editor.fireIsDirty(); when the corpus is modified (create, delete, edit annotations) with the annotation toolbar or with the ElementPropertyView
editor.isDirty calls all ToolbarButton.isDirty() methods
and editor.doSave calls all ToolbarButton.doSave() methods