Quote:
Originally Posted by icearch
So, in conclusion:
1. No matter continuous or not, moving up or down, all should stop moving when the most front ones hits boundary. Which is not what happens now.
2. Moving down fundamentally broken ,needs fix.
|
About 1: Here we disagree. How it operates with an illegal selection with a multi-selection is to drop the part that is illegal but continue performing any legal selections. Why should a single illegal selection stop other legal items from moving? If a user goes too far, they can easily fix reverse to fix it.
And that is what the code did in all cases of moving up, right and left. In all of your "spamming" cases you had illegal selections in a multi-selection for a move direction you did and just that part was ignored. Nothing in these cases are random. It did what you asked when the move direction hit a boundary with an item that can not move in that direction, and dropped it automatically from the multi-selection.
You seem to think of what you select as a "solid block" that should only move until it reaches an edge. Where-as I conceived them as a collection of selected items that you told to move in a specific direction and it does its best to carry out what you asked on each part of the collection only ignoring something when it is illegal to move in that direction.
So it may be not what you expected but it was exactly what I expected as that was the design of the code. So we will disagree here.
About 2: Agreed. I will look into that.