The restarting engines command breaks the annotations saving operation
Currently, the annotations saving operation can be very long.
Users tend to call the ‘File >Restart engines’ command, hoping that something will get cleared but braking the annotations saving operation.
Users can even quit TXM, hoping they will get control afterwards.
As a long operation!
- TXM must show the progression of the operation, like what is done for other time consuming commands
- TXM must display the status of the operation: the user must understand to wait
Solution 1
The XML-TXM update steps were not wrap in a Job ->allowing the restart command to run before the annotation are saved
Add the following message in jobs/console:
- FR: Merci de ne pas quitter TXM tant que cette opération n’est pas terminée (risque de corruption des données)
- EN: Please do not quit TXM until this operation is completed (risk of data corruption)]
Solution 2 (see #2986)
a. remove ‘File >Restart engines’ menu entry
b. open a modal dialog box displaying the progression of the annotations saving operation
TXM is currently using Eclipse Jobs to run operations. The jobs are started using the Job.schedule() method which ensures jobs are started in order but do not block the other jobs.
- The Job priority only drives the job start time.
- The Job rule is to strict and does not allow to run a Job from another job (ex: cannot save RCP project while importing a corpus in a job)
- The job family (see Job.belongsTo method) only allow to pilot a group of Job
partial solution: https://wiki.eclipse.org/FAQ\\\_How\\\_do\\\_I\\\_prevent\\\_two\\\_jobs\\\_from\\\_running\\\_at\\\_the\\\_same\\\_time%3F ->does not works when a ROOT level sub job is called (RCP project saving)
(from redmine: issue id 2879, created on 2020/07/23 by Serge Heiden)
Validation test
- Annotate all VOEUX words with an annotation
- During the process try to restart the engines
- A messages is shown in console and engines are not restarted