| Summary: | [Model Explorer] [Performance] Moving many elements from one package to another takes too much time | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Alain Le Guennec <alain.leguennec> | ||||
| Component: | Core | Assignee: | Project Inbox <mdt-papyrus-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | eclipse-bugzilla, yann.tanguy | ||||
| Version: | 0.8.1 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Alain Le Guennec
Created attachment 207149 [details]
The model used to reproduced the issue.
the movement of children for this example takes as much time. However the start of the movement can take a bit of time (3or 4) time to creating queries. done in the revision 6275 I have also combined with another command thanks to remarks from Yann. If the drop seems to be a change order, sometimes there is also a reparent. If a request to of move is not done, associated diagram and UML semantic can be incorrect. A test has been added to add this command if necessary. Now the execution of the test case take 3 or 4 seconds. A technical documentation will be added in the wiki. done in the revision 6291 A small explanation has been added in the wiki: http://wiki.eclipse.org/Papyrus_Developer_Guide/Papyrus_Structure_Behavior |