Bug 405589 - [StateMachineDiagram] Papyrus StateMachine Diagram Editor shall enable model elements to be moved inside or outside a composite state.
Summary: [StateMachineDiagram] Papyrus StateMachine Diagram Editor shall enable model ...
Status: ASSIGNED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Diagram (show other bugs)
Version: 0.10.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Ansgar Radermacher CLA
QA Contact:
URL:
Whiteboard:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2013-04-12 10:01 EDT by Samuel Rochet CLA
Modified: 2017-08-02 11:38 EDT (History)
1 user (show)

See Also:

Attachments
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 Samuel Rochet CLA 2013-04-12 10:01:44 EDT 
[StateMachineDiagram] In the state machine diagram, elements cannot be moved inside or outside a composite state. 
A workaround is possible but painful: You must move it in model explorer first, drag and drop it in the composite state and delete graphically the old figure
Comment 1 Ansgar Radermacher CLA 2013-05-21 09:50:50 EDT 
Should be fixed in revision 11161 of trunk.
A reparent operation is now supported. During this operation, the containers of affected transitions are (eventually) updated.
Comment 2 Ansgar Radermacher CLA 2013-05-21 16:07:42 EDT 
There is an issue that is not well handled by the current bug-fix:

If the state that is dragged into a composite is visualized in a different state diagram (or duplicated in the same diagram), these other occurrences are not updated accordingly. We need to remove these occurrences of a "re-parented" state from other diagrams. However, the user might not be aware that these side-effects of the move operation. If other occurrences of the same state exist in other diagrams, papyrus should ask the user in a dialog, if he really wants to execute a reparent operation.

Btw. this problem existed already before the current fix, since moving into a composite state via the model explorer does not imply diagram updates at all.