Feature #2450
Persist the user modifications done on a lexical table
Status: | New | Start date: | 09/14/2018 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% |
|
Category: | Persistence / Lazy | Spent time: | - | |
Target version: | TXM 0.8.4 |
Description
- problème des tables lexicales modifiées par l'utilisateur
- les modifications (fusion/suppression de colonnes ou lignes) sont perdues au changement d'un paramètre après le recalcul
- [SJ: à mon sens la suppression devrait être gérée autrement, à savoir, ne pas effacer ces lignes mais les marquer comme non sélectionnées]
- les modifications ne sont pas sauvegardées/rechargées
History
#1 Updated by Sebastien Jacquot over 4 years ago
- Description updated (diff)
#2 Updated by Matthieu Decorde about 4 years ago
- Target version changed from TXM 0.8.0 to TXM 0.8.2
#3 Updated by Matthieu Decorde about 2 years ago
Content of #2545 closed (duplicated) :
Lexical Table user edition is not persisted between sessions and no message alert him.
Solution¶
- discuss about the possibility to mark/unmark some matrix rows/cols rather than really suppress or fuse them
- find a way and a format to store these markers (suppression and fusion) to recreate the result
- thought about the solution of store "data" result in the .*prefs persistance file, eg. for LT => the R data, for charts => the file data or the serialized Java object
#4 Updated by Matthieu Decorde about 2 years ago
- Target version changed from TXM 0.8.2 to TXM 0.8.4