Community
Participate
Working Groups
TreeViewerTransferDropListener.getCommand() iterates the TreeViewerTransfer items, gathering a command for each one separately. This causes a problem when multiple objects are dragged to a location in front of their current one. If each item is going to the same index, each subsequent object will be placed in front of the previous one, reversing their original order, even though they were being dragged together. It would be best to package up all the objects in a single command rather than iterating and gathering commands for each separately. This problem is clearly visible in the Logic example. Add several items, select a couple of adjacent ones in the outline and drag them upwards. They will be left in the reverse order in which they appeared originally.
Has anything been done on this? Thanks.
Created attachment 50498 [details] Potential bug fix This changes getting a REQ_MOVE command from each child with getting REQ_MOVE_CHILDREN command from parent for the case where isMove() is true. That allows command to be aware of other children being moved rather than each child being moved in isolation.
*** Bug 156100 has been marked as a duplicate of this bug. ***
Without removing the necessity of performing the change suggested in the attach file, I think making all class required to use the drag & drop in the tree viewer public could increase the flexibility available to programmer.
Unset target milestone as the specified one is already passed.
