Bug #2686

When setting a result to non persistent, its parent may be hidden and never be deleted

Ajouté par Sebastien Jacquot il y a presque 6 ans. Mis à jour il y a plus d'un an.

Statut:Feedback Début:03/12/2019
Priorité:Normal Echéance:
Assigné à:- % réalisé:

70%
Catégorie:Persistence / Lazy Temps passé: -
Version cible:TXM 0.8.4

Description

Some commands create intermediate hidden results to compute the final target result.
Eg. a CA from a Partition creates an hidden Lexical Table needed by the CA command.
When making the CA persistent, its parent is made persistent too.
But when making back the CA non-persistent, the parent LT stays persistable leading to keep some "ghost" results, stored in .prefs files and reloaded at TXM start but invisible in the UI.

Solution 1

Manage the user persistable state ascending and descending propagation according to some state of parent and children (hidden/visible, must be synchronized with parent, etc.)

Validation tests

//TO DEFINE

Révisions associées

Révision 2533
Ajouté par Sebastien Jacquot il y a plus de 5 ans

Fixes: When setting a result to non persistent, its parent may be hidden and never be deleted (refs #2686)
Fixes: a bug that leads to infinite loop and introduced by a previous fix of #2686

Historique

#1 Mis à jour par Sebastien Jacquot il y a presque 6 ans

  • Description mis à jour (diff)

#2 Mis à jour par Sebastien Jacquot il y a plus de 5 ans

  • Description mis à jour (diff)
  • Statut changé de New à Feedback
  • Version cible changé de TXM 0.8.2 à TXM 0.8.1
  • % réalisé changé de 0 à 70

Fixed using a new argument to proceed deep recursively or not in org.txm.core.results.TXMResult.setUserPersistable(boolean, boolean).
Also added the management of persistable states of children of result that must always be synchronized with their children to be consistent.

#3 Mis à jour par Sebastien Jacquot il y a plus d'un an

  • Version cible changé de TXM 0.8.1 à TXM 0.8.4

Formats disponibles : Atom PDF