Aseprite version: v1.3.15.4-x64
Platform: Windows 10
Tablet: Huion HS610
Happens almost everytime I accidentaly move a layer quickly with LeftCtrl + LeftMouseButton(in my case tapping the pen on the tablet). Ctrl+Z ignores the layer movement and doesn’t move it back, as if that was the original position of the layer.
A topic about this issue already existed, but it was very old. I’m sorry if I should not have made a new one with the same bug report, just wanted to bring attention to this again.
I’m also having the same issue, in my case it happens when I CTRL+LeftClick and drag to move a layer.
Ctrl+Z doesn’t undo the movement.
And it is specially annoying when the layer gets moved just a pixel because sometimes is hard to notice is not on the right spot until the issue has snowballed into a huge mistake.
As a note, I’ve been trying to reproduce this bug intentionally for ages without luck, so I don’t know what triggers it nor how to avoid it.
Aseprite Version: v1.3.16-beta2-x64
Platform: Windows 10, Windows 11.
Tablet: Wacom Cintiq Pro 13, Wacom Cintiq Pro 24. Also happens with the mouse.
I was able to recreate it pretty consistently by using the Move Tool(V) and spamming Left Click and dragging the layer at the same time while spamming Ctrl+Z(this time using a mouse instead of a drawing tablet). At some point the undo ignores that it moved and refuses to go back to the original position. It might be some weird timing when you move the layer with the Move Tool(both with V and Ctlr+LeftClick) and also press Ctrl+Z.
Although I could recreate it a lot of times, the method was kind of random by spamming the mentioned keys. I was not able to figure out a clear way of recreating it.
The biggest problem for me is the fact that it throws off the workflow and can mess up tiles if not careful.
Was also able to recreate it by dragging the layer with the Move Tool without spamming LeftClick, just spamming Ctrl+Z while constantly moving the layer. While moving sometimes the Ctrl+Z just stops the layer at the current position and doesn’t undo the full movement. I don’t know for sure if it has something to do with part of the layer being out of bounds of the image, I doubt it, but might be something worth looking into.
Looks like a very hard bug to pull of, but it happens quite often while I’m working(for such a specific bug ofc). So much so that I decided to create this report.