Bug #2686
Mis à jour par Sebastien Jacquot il y a plus de 5 ans
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.
h3. Solution 1
Manage We already propagate the user persistable state ascending and descending propagation according persistence to some state of parent and children (hidden/visible, must be synchronized with parent, etc.)
h3. Validation tests
//TO DEFINE when it's defined to true.
We may also propagate it if defined to false AND the parent is hidden?
Are there any side effects?
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.
h3. Solution 1
Manage We already propagate the user persistable state ascending and descending propagation according persistence to some state of parent and children (hidden/visible, must be synchronized with parent, etc.)
h3. Validation tests
//TO DEFINE when it's defined to true.
We may also propagate it if defined to false AND the parent is hidden?
Are there any side effects?