Bug #2351
Mis à jour par Serge Heiden il y a plus de 7 ans
Currently, reloading a CQP corpus in the current session (search engine restart) can lead to a "corpus not ready" status whereas the corpus could be correct.
There are two status messages :
* "corpus not ready" status when corpus selected
* "corpus not ready" in the console
We should propose to the user to restart TXM as soon as we diagnose the problem. TXM.
h3. Solution
# after each import or corpus load, check corpus status
# if status not ready -> open modal dialog box :
** with the message :
*** "Le moteur de recherche ne parvient pas à accéder au corpus $X. Le problème peut peut-être être résolu en quittant puis en relançant TXM."
*** "The search engine cannot access the $X corpus. The problem may be resolved by quitting and restarting TXM."
** and a single OK button to close the dialog box with no action.
There are two status messages :
* "corpus not ready" status when corpus selected
* "corpus not ready" in the console
We should propose to the user to restart TXM as soon as we diagnose the problem. TXM.
h3. Solution
# after each import or corpus load, check corpus status
# if status not ready -> open modal dialog box :
** with the message :
*** "Le moteur de recherche ne parvient pas à accéder au corpus $X. Le problème peut peut-être être résolu en quittant puis en relançant TXM."
*** "The search engine cannot access the $X corpus. The problem may be resolved by quitting and restarting TXM."
** and a single OK button to close the dialog box with no action.