You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Select part of the sprite using the rectangular marquee tool.
Copy the selection (using Edit|Copy or by pressing Ctrl+C).
Paste previously copied rectangle (through Edit|Paste or Ctrl+V).
What is the expected output? What do you see instead?
Menu commands like Edit|Flip Vertical or Edit|Flip Horizontal or even Edit|Paste should be active. Instead, they appear as disabled. However, they can be still accessed through keyboard shortcuts. What version of the product are you using? On what operating system? Aseprite 0.9.5 on Windows 8 64-bit.
I have looked a little bit into this problem, but not enough to say exactly what is causing it. I suspect it's the result of a disconnect between being a Selection and MovingPixels. For whatever reason when an image is pasted, it looks like there's a selection but it isn't really treated like one.
This problem is because MovingPixelsState contains a PixelsMovement, which contains an UndoTransaction. This undo transaction lock the document in write mode in the whole transformation process of the pasted/moved image. It's quite hard to solve this. There are a "to do" item related with this which consist on adding undo to each transformation phase (e.g. you rotate, then scale, the move, there should be three different undo steps).
From olsze...@gmail.com on October 17, 2013 16:42:09
What steps will reproduce the problem?
What is the expected output? What do you see instead?
Menu commands like Edit|Flip Vertical or Edit|Flip Horizontal or even Edit|Paste should be active. Instead, they appear as disabled. However, they can be still accessed through keyboard shortcuts. What version of the product are you using? On what operating system? Aseprite 0.9.5 on Windows 8 64-bit.
Original issue: http://code.google.com/p/aseprite/issues/detail?id=275
The text was updated successfully, but these errors were encountered: