Bug #2351

RCP: 0.7.9, CQP corpus re-load "not ready" user message

Added by Serge Heiden over 1 year ago. Updated 8 months ago.

Status:New Start date:03/06/2018
Priority:Normal Due date:
Assignee:- % Done:

80%

Category:Import Spent time: -
Target version:TXM 0.8.0

Description

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.

Solution

  1. after each import or corpus load, check corpus status
  2. 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.

Related issues

related to Bug #966: TBX: 0.7.6, import module abort causes corrupted original... Feedback 08/06/2014
related to Bug #974: TBX: 0.7.6, corpus load abort causes corrupted corpus New 08/08/2014
related to Bug #2339: RCP: 0.7.9, XTZ import module (and others), "Corpus not r... New 02/08/2018
related to Bug #2352: RCP: 0.7.9, CQP corpus re-load "not ready" New 03/06/2018

History

#1 Updated by Serge Heiden over 1 year ago

  • Description updated (diff)

#2 Updated by Serge Heiden over 1 year ago

  • Description updated (diff)

#3 Updated by Sebastien Jacquot over 1 year ago

  • Target version changed from TXM 0.8.0a (split/restructuration) to TXM 0.8.0

#4 Updated by Matthieu Decorde 8 months ago

  • % Done changed from 0 to 80

Also available in: Atom PDF