Bug #2742
Mis à jour par Sebastien Jacquot il y a plus de 5 ans
TXMEditor parameters parameter toolbar is broken when a CQP corpus is not ready -> CQP exception are raised.
E.g. This is more general, we need to ensure the result parent is ready to be used.
eg: calling Cooccurrence on a Subcorpus not computed Sub-corpus throws a throw an CQP exception when the Cooccurrence editor is opened and tries try to load the available corpus properties.
h3. Solution 1
When opening a TXMEditor always pre-compute the parent before. Add parent.compute(false) in
* a) A- TXMEditor.openEditor()
* b) B- TXMEditor.this.createPartControl
a) A: can manage the parent.compute in a job
b) B: always works but might cause freezes at any moment. -> maybe we can use a busyWhile job to correctly freezes correclty freeze the interface
---> Use the b) B solution and validate the freeze is ok
h3. Solution 3 2
* protect all TXMResult getters methods with a this.compute(false)
E.g. This is more general, we need to ensure the result parent is ready to be used.
eg: calling Cooccurrence on a Subcorpus not computed Sub-corpus throws a throw an CQP exception when the Cooccurrence editor is opened and tries try to load the available corpus properties.
h3. Solution 1
When opening a TXMEditor always pre-compute the parent before. Add parent.compute(false) in
* a) A- TXMEditor.openEditor()
* b) B- TXMEditor.this.createPartControl
a) A: can manage the parent.compute in a job
b) B: always works but might cause freezes at any moment. -> maybe we can use a busyWhile job to correctly freezes correclty freeze the interface
---> Use the b) B solution and validate the freeze is ok
h3. Solution 3 2
* protect all TXMResult getters methods with a this.compute(false)