Bug 441176 - Wrong Delete Behavior when deleting Sync or Async Calls
Summary: Wrong Delete Behavior when deleting Sync or Async Calls
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Diagram (show other bugs)
Version: 1.0.0   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2014-08-05 09:03 EDT by Alex Lagarde CLA
Modified: 2014-08-06 11:12 EDT (History)
1 user (show)

See Also:

Attachments
SequenceDiagram project (2.60 KB, application/x-zip-compressed)
2014-08-05 09:03 EDT, Alex Lagarde CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Lagarde CLA 2014-08-05 09:03:04 EDT 
Created attachment 245723 [details]
SequenceDiagram project

Steps to reproduce: 
- Create an interaction model,activate the "Interaction" Viewpoint from Sirius example and create a Sequence Diagram (or import the attached modeling project)
- Create a Sync Call or an Async call (one a single lifeline or from one Participant to another)
- Delete the Execution
- KO: The messages stay, but it is impossible to delete the top message
- Close & reopen the editor : deletion is now possible
Comment 1 Pierre-Charles David CLA 2014-08-06 11:11:48 EDT 
Confirmed. Note that the fact that the messages stay (and are reconnected to the lifeline) when the execution is deleted is the expected behavior. What is problematic here is that after the execution has been deleted the top message can neither be moved nor deleted.