Bug 478039

Summary:	Possibility to reorder elements of a list in a container
Product:	[Modeling] Sirius	Reporter:	Melanie Bats <melanie.bats>
Component:	Diagram	Assignee:	Project Inbox <sirius.diagram-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	dominik.mosen, info, miklossy, pierre-charles.david, thanhliem.phan
Version:	3.0.0	Keywords:	triaged
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Melanie Bats

2015-09-22 05:35:58 EDT

It should be possible to change the order of elements of a list in a container.
The Drop tool doesn't allow to drop element in the same container, and, in another container, it is not possible to select the place in the list.

Comment 1 Pierre-Charles David

2015-09-22 08:29:25 EDT

I see two possible interpretations:
1. Changing the visual order of elements, without touching the underlying model. Might not be possible (or at least complex to implement and understand), as the current visual order depends on the order of mappings in the VSM and the order in which their semanticCandidates are returned. Mixing that with UI-level "preferences" would lead to complex behaviors.
2. Allowing tools defined in the VSM to react (arbitrarily) to user interactions which correspond to dragging a list item at another position in the same list. Something similar to the ReorderTool from sequence diagrams. The tool would be given all appropriate information (which element was moved, and to which position in the list), and could react in any way. The next refresh would use the current rule to derive the actual graphical order of list items. It would be the tool's reponsibility to change the underlying model so that the semanticCandidates return the elements in the (new) order.

Mélanie, can you confirm solution 2 would fit your need?

Comment 2 Melanie Bats

2015-09-23 10:07:12 EDT

Yes, the second solution would be perfect! The tool should work not only when one element would be selected but also with a multiple elements selection.

Comment 3 Tamas Miklossy

2019-01-29 07:31:06 EST

When is this ticket planned to be fixed?