Bug #2742
Mis à jour par Sebastien Jacquot il y a plus de 5 ans
TXMEditor parameters toolbar is broken when a CQP corpus is not ready -> CQP exception are raised.
E.g. calling Cooccurrence on a not computed Sub-corpus throws a CQP exception when the Cooccurrence editor is opened and tries 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) TXMEditor.openEditor()
* b) TXMEditor.this.createPartControl
a) can manage the parent.compute in a job
b) always works but might cause freezes at any moment. -> maybe we can use a busyWhile job to correctly freezes the interface
---> Use the b) solution and validate the freeze is ok
h3. Solution 2 3
* protect all TXMResult getters methods with a this.compute(false)
h3. Validation tests
WIP SJ:
* purpose here is to test on large corporas that contain not computed partitions or corpus that calling a command or reopening a result that are descendant to the not computed objects works as expected
E.g. calling Cooccurrence on a not computed Sub-corpus throws a CQP exception when the Cooccurrence editor is opened and tries 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) TXMEditor.openEditor()
* b) TXMEditor.this.createPartControl
a) can manage the parent.compute in a job
b) always works but might cause freezes at any moment. -> maybe we can use a busyWhile job to correctly freezes the interface
---> Use the b) solution and validate the freeze is ok
h3. Solution 2 3
* protect all TXMResult getters methods with a this.compute(false)
h3. Validation tests
WIP SJ:
* purpose here is to test on large corporas that contain not computed partitions or corpus that calling a command or reopening a result that are descendant to the not computed objects works as expected