Bug #2879
Mis à jour par Matthieu Decorde il y a plus de 4 ans
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
h3. Solution 1
The XML-TXM update steps were not wrap in a Job -> allowing the restart command to run before the annotation are saved
h3. 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)
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
h3. Solution 1
The XML-TXM update steps were not wrap in a Job -> allowing the restart command to run before the annotation are saved
h3. 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)