Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Undo/redo each step of selection transformations step-by-step #424

Open
aseprite-bot opened this issue Aug 20, 2014 · 4 comments
Open

Undo/redo each step of selection transformations step-by-step #424

aseprite-bot opened this issue Aug 20, 2014 · 4 comments
Labels
feature Feature request, or something should be improved high priority imported refactor complexity This issue needs some refactor / modifying several files / rethinking some part of the architecture ui
Milestone
v1.3.x

Comments

@aseprite-bot
Copy link
Collaborator

From davidcapello on July 16, 2014 22:25:22

What do you need to do?
Select a portion of the sprite, move it, rotate it, scale it, and then undo step-by-step (first we should be able the undo the scalation, then the rotation, the translation, and finally the selection).

How would you like to do it?
With the normal Ctrl+Z or Edit > Undo action.

Original issue: http://code.google.com/p/aseprite/issues/detail?id=424
@dacap dacap removed the undo label Aug 31, 2014
@dacap
Copy link
Member

dacap commented Aug 31, 2014

Note: the transformation should be done in a temporal "floating" layer that should be part of the sprite. In this way we don't need to do all transformations in a whole "undo transaction".

@dacap dacap added this to the v1.0 milestone Aug 31, 2014
@dacap dacap self-assigned this Aug 31, 2014
@dacap dacap modified the milestones: v1.1, v1.0 Aug 31, 2014
@dacap
Copy link
Member

dacap commented Jun 2, 2015

Related issues to this one #690 and #275

dacap added a commit that referenced this issue Jun 2, 2015
@dacap
Patch a possible crash when dropping pixels onBeforeFrameChanged
61c745e 
This is not a "real fix". But we hope the program at least doesn't crash
in this scenario.

Reviewed this problem on #275, #424, and #690
@dacap
Copy link
Member

dacap commented Aug 28, 2015

This change is too big for v1.1

@dacap dacap modified the milestones: v1.2, v1.1 Aug 28, 2015
@KasumiArai KasumiArai mentioned this issue Feb 16, 2016
Open
@dacap dacap mentioned this issue Apr 18, 2017
Open
10 tasks
@dacap dacap modified the milestones: v1.3, v1.4 Sep 12, 2017
@dacap dacap mentioned this issue Nov 5, 2018
Open
@dacap dacap added the refactor complexity This issue needs some refactor / modifying several files / rethinking some part of the architecture label Nov 5, 2018
@dacap dacap modified the milestones: v1.4, v1.3 Nov 5, 2018
@dacap
Copy link
Member

dacap commented Nov 17, 2021

Related https://community.aseprite.org/t/disable-multi-step-undo/11792

@dacap dacap mentioned this issue Jun 8, 2022
Open
@dacap dacap removed their assignment Sep 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature Feature request, or something should be improved high priority imported refactor complexity This issue needs some refactor / modifying several files / rethinking some part of the architecture ui
Projects
None yet
Milestone
v1.3.x
Development

No branches or pull requests
2 participants
@dacap @aseprite-bot