Bug 420571 - [All diagrams] Reorder attributes, operations, parameters etc.
Summary: [All diagrams] Reorder attributes, operations, parameters etc.
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: Diagram (show other bugs)
Version: 1.1.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 455498 (view as bug list)
Depends on: 420549
Blocks: 381568 394923
  Show dependency tree
 
Reported: 2013-10-28 19:17 EDT by Toni Siljamäki CLA
Modified: 2017-09-08 11:18 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Toni Siljamäki CLA 2013-10-28 19:17:38 EDT
Clearly show the possibility to move attributes/operations/parameters/etc.
up and down in Model Explorer, perhaps with new right-click-move menus.
(would be nice if we could move them up and down also in diagrams)
Comment 1 Toni Siljamäki CLA 2013-10-29 05:53:31 EDT
Having for instance parameters in the "correct" order is important when
integrating code generated from models with existing and read-only legacy code.

Today there is a possibility to reorder elements in a model only by dragging
them in the ModelExplorer, which is a quite risky and error prone operation.

Example:
In Model Explorer you can drag an attribute up-and-down and quite easily
drop it into another attribute by mistake. Since Model Explorer responds
so slowly for larger models, it may take quite some time to detect
such mistakes. This type of micro-crashes may take a long time to repair.

For that reason it could be wise to disable this drag-and-dropping in
Model Explorer to prevent mistakes and only allow reordering via menus.
Comment 2 Camille Letavernier CLA 2013-11-12 08:53:26 EST
Elements should be ordered (graphically), even when the underlying collection is not order (Such as Class#ownedAttribute: semantically, the collection is not ordered, but it should still be possible to re-order elements)
Comment 3 Toni Siljamäki CLA 2013-11-14 10:14:26 EST
Just to make it clear:

The order we can see in Model Explorer is the order that should be displayed
in the diagram (and vice versa) and is the order we could expect by default
in generated code when transforming a model into code.

This is often of utmost importance when integrating generated code
with existing code, previously generated and/or handwritten code.
Comment 4 Toni Siljamäki CLA 2013-11-14 10:15:40 EST
By that I mean that there cannot be any mismatch in the ordering of things.
Comment 5 Patrick Tessier CLA 2014-03-20 16:38:26 EDT
so this task is linked to a sunchronization between model explorer and diagram
Comment 6 Camille Letavernier CLA 2014-12-18 04:13:25 EST
*** Bug 455498 has been marked as a duplicate of this bug. ***
Comment 7 Toni Siljamäki CLA 2015-04-11 10:53:58 EDT
Still valid.
...and e.g operations cannot be reordered in diagrams.

Reordering by dragging in Model Explorer is not reflected in diagrams.