Community
Participate
Working Groups
When a container contains a node, and if the container mapping has a non-default delete tool, the result of selecting both the container and node and hitting "Delete" is different depending on the order of selection (which is not easily user-controllable).
Created attachment 276611 [details] Sample project to reproduce the issue Steps to reproduce: 1. Import the attached project and open the diagram ("new delete-composition"). 2. Select the "B1" node inside "A1" and hit "Delete" => "B1" is removed from the model and both views disappear. "A1" is still there. OK. 3. Undo to go back to the initial state. 4. Select "A1" and hit delete => the "A1" semantic element (and view) is removed. The delete tool on A1 is a custom one which just removes the current element, so "B1" is still present in the model, and the top-level view is still there. OK. 5. Undo to go back to the initial state. 6. Select "B1" and then "A1", in this order, using shift-click to add "A1" to the selection. Hit delete => both selected elements (and all views) are removed. OK. 7. Undo to go back to the initial state. 8. Select "A1" and then "B1", in this order, using shift-click to add "B1" to the selection. Hit delete => "A1" (and its view) is removed, but "B1" is still present in the model. KO #1 => despite B1 being part of the selection, the corresponding delete tool (here the default) has not been invoked. KO #2 (related) => the final state depends on the selection order between the container and contained element.
Created attachment 276612 [details] Sample video illustrating the reproduction steps
