Community
Participate
Working Groups
Assuming a very simple model with just two packages and 1024 blocks in one of the packages, select all blocks and move them all at once into the second package. => The move operation takes an inordinate amount of time to complete (about half an hour on my machine). The blocks themselves have no nested properties or diagrams, and are not referenced by anything, so there does not seem to be anything complicated to propagate in term of impact on the model while performing the move, which suggests that there might be an algorithm complexity issue somewhere.
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
