Selected Objects Occasionally Slide at Different Scales

[AdrianGroty]

Sometimes, certain selected objects will respond to shift+h/j/k/l as if receiving two slide commands, but all others will behave as expected. It has a sort of "parallax scrolling" effect, in action.

I'm not sure how to trigger this bug on command, but it do be happening. I conjecture that it has something to do with complex selections of objects stacked on top of each other in the same x/y coordinates.

[saulpw]

I only have one theory for how this could happen, and that's if that literal row object (not a copy but the actual reference) is in the list of rows twice. Then the loop would adjust it twice, causing the kind of behavior you see here. So the problem is not with slide, but with some previous action that managed to add a duplicate row reference instead of a copy. I've tried a few things, but without more information I can't see what would cause that. Best we can do is add an assertion in addRow that makes sure the row reference doesn't already exist, so we can catch the problem as it happens. This will probably cause a performance issue for some commands in large drawings so we shouldn't leave it there permanently.

I bet that in this case, if you saved the file and reloaded it, this behavior would go away.

[AdrianGroty]

Un/Reselecting the same selection resulted in the same parallax movement, but saving and reloading the file does correct it.

[saulpw]

Had you updated to this latest code already when it happened again? If so then that assert must not have fired, and therefore my understanding of this bug is wrong. Please confirm one way or the other.

[AdrianGroty]

git log shows a commit on Jan 20 for [addRow]. I do not believe I have pulled since my previous comment.