Bug #2633

Deleting a cloned result also deletes the original result

Added by Sebastien Jacquot over 3 years ago. Updated almost 3 years ago.

Status:New Start date:10/30/2019
Priority:High Due date:
Assignee:- % Done:

80%
Category:Commands Spent time: -
Target version:TXM 0.8.1

Description

When a Result is created with hidden parents, the delete command deletes the parent.
But if the result is cloned, both results are deleted

Solution

Delete parent only if :
  • hidden
  • AND has no more child

Associated revisions

Revision 2460
Added by Matthieu Decorde about 3 years ago

fix TXMResult delete command refs #2633

Revision 2572
Added by Sebastien Jacquot about 3 years ago

Fixes: Deleting a cloned result also deletes the original result (refs #2633)

History

#1 Updated by Sebastien Jacquot over 3 years ago

  • Subject changed from Deleting a cloned specificities also delete the original specificities to Deleting a cloned specificities also deletes the original specificities

#2 Updated by Sebastien Jacquot over 3 years ago

  • Subject changed from Deleting a cloned specificities also deletes the original specificities to Deleting a cloned result also deletes the original result
  • Description updated (diff)

#3 Updated by Matthieu Decorde about 3 years ago

  • Subject changed from Deleting a cloned result also deletes the original result to Deleting a cloned specificties or AFC result computed from partition
  • Description updated (diff)
  • Category set to Commands

#4 Updated by Matthieu Decorde about 3 years ago

  • % Done changed from 0 to 80

#5 Updated by Sebastien Jacquot about 3 years ago

  • Target version changed from TXM 0.8.2 to TXM 0.8.1

#6 Updated by Sebastien Jacquot about 3 years ago

  • Subject changed from Deleting a cloned specificties or AFC result computed from partition to Deleting a cloned result also deletes the original result

#7 Updated by Sebastien Jacquot about 3 years ago

  • % Done changed from 80 to 0

The fix doesn't work...
Update: my bad... I reintroduced the bug by commenting:

parent.getChildren().size() == 1 // AND if there is no sibling

in DeleteObject, line 127, several days ago.

I think this test is not sufficient to manage all the case of deletion.
I'll do some tests.

#8 Updated by Sebastien Jacquot almost 3 years ago

  • % Done changed from 0 to 80

Also available in: Atom PDF