Community
Participate
Working Groups
Drag and drop is not well supported for all elements of sequence diagrams. Dnd should be supported for all elements. Moreover, it would be interesting to have an advanced drag and drop support for some elements. For instance, a drag and drop of a ConnectableElement on an Interaction should create a Lifeline and reference the dropped ConnectableElement in the Lifeline "represents" property. A generic solution may be possible.
Created attachment 212084 [details] Bug fix
Created attachment 213738 [details] DnD Support for all elements except the nested combined fragment
The patch does not work for combined fragments, even if there are not nested. However, the proposed patch covers other elements. The patch has been commited on the trunk r.7959.
What do you mean it does not work for combined fragments. Could you detail the issue ?
Created attachment 214459 [details] fix the size problem of combined fragment to enclose all lifelines
Created attachment 214461 [details] fix the size problem of combined fragment to enclose all lifelines
Created attachment 214462 [details] fix the size problem of combined fragment to enclose all lifelines
Created attachment 214463 [details] fix the size problem of combined fragment to enclose all lifelines
Created attachment 214466 [details] Fixes the combined fragment size problem and lifeline DnD
Changes committed on the trunk r.7969
When a message is dragged on the diagram whereas it source and/or target lifeline is not present on the diagram, the missing lifeline(s) is displayed for that message, but the message is not displayed. Moreover, the displayed lifeline is not aligned properly.
- Message When we DnD a message from model explorer, the both connected lifelines must have the graphical presentation in the diagram. Otherwise, an error message will show up to indicate the missing lifeline(s). If the message is connected via Action/Behavior Executions, they should be added automatically if they are missing. The nested Action/Behavior Executions should also be supported. - ConbinedFragment When we DnD a CF, it should enclose the referenced message links hold by its operants. That means the size and position should be calculated with the position of the message links.
closed
