Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 364696

Summary:

[Sequence Diagram] - Advanced drag and drop support

Product:

[Modeling] Papyrus

Reporter:

Chokri Mraidha <Chokri.Mraidha>

Component:

Core

Assignee:

Chokri Mraidha <Chokri.Mraidha>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

yves.yang

Version:

0.9.0

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

Attachments:

Description	Flags
Bug fix	none
DnD Support for all elements except the nested combined fragment	sebastien.gerard: iplog+
fix the size problem of combined fragment to enclose all lifelines	none
fix the size problem of combined fragment to enclose all lifelines	none
fix the size problem of combined fragment to enclose all lifelines	none
fix the size problem of combined fragment to enclose all lifelines	none
Fixes the combined fragment size problem and lifeline DnD	sebastien.gerard: iplog+

Description Chokri Mraidha

2011-11-24 05:27:13 EST

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.

Comment 1 Yves YANG

2012-03-05 12:20:37 EST

Created attachment 212084 [details]
Bug fix

Comment 2 Yves YANG

2012-04-09 02:58:50 EDT

Created attachment 213738 [details]
DnD Support for all elements except the nested combined fragment

Comment 3 Chokri Mraidha

2012-04-23 05:52:10 EDT

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.

Comment 4 Yves YANG

2012-04-23 06:25:44 EDT

What do you mean it does not work for combined fragments. Could you detail the issue ?

Comment 5 Yves YANG

2012-04-24 07:52:33 EDT

Created attachment 214459 [details]
fix the size problem of combined fragment to enclose all lifelines

Comment 6 Yves YANG

2012-04-24 08:07:04 EDT

Created attachment 214461 [details]
fix the size problem of combined fragment to enclose all lifelines

Comment 7 Yves YANG

2012-04-24 08:08:41 EDT

Created attachment 214462 [details]
fix the size problem of combined fragment to enclose all lifelines

Comment 8 Yves YANG

2012-04-24 08:12:54 EDT

Created attachment 214463 [details]
fix the size problem of combined fragment to enclose all lifelines

Comment 9 Chokri Mraidha

2012-04-24 09:27:53 EDT

Created attachment 214466 [details]
Fixes the combined fragment size problem and lifeline DnD

Comment 10 Chokri Mraidha

2012-04-24 09:28:24 EDT

Changes committed on the trunk r.7969

Comment 11 Chokri Mraidha

2012-07-09 06:11:11 EDT

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.

Comment 12 Yves YANG

2012-07-09 18:43:36 EDT

- 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.

Comment 13 Sébastien Gérard

2013-02-12 04:50:57 EST

closed