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

Data loss prevention in case of crash #151

Closed
aseprite-bot opened this issue Aug 20, 2014 · 1 comment
Closed

Data loss prevention in case of crash #151

aseprite-bot opened this issue Aug 20, 2014 · 1 comment
Assignees
Labels
critical priority feature Feature request, or something should be improved imported logic
Milestone

Comments

@aseprite-bot
Copy link
Collaborator

From davidcapello on August 07, 2012 10:09:10

We need a way to prevent data loss, at least to some certain recent point of the sprite before a crash (in the best case, in the exact point of the crash).

It could be done continually saving each sprite transformation/action into a file. So when the program crashes we can read the stream of operations to recreate the history of the sprite. If the sprite is saved correctly, we can discard the list of operations.

Other way is to create periodic snapshots of highly modified canvases. (Anyway it would need a way to create the snapshots in background without locking the whole sprite.)

Original issue: http://code.google.com/p/aseprite/issues/detail?id=151

@aseprite-bot aseprite-bot added this to the v1.1 milestone Aug 20, 2014
@dacap dacap modified the milestones: v1.3, v1.1 Sep 19, 2014
@dacap dacap modified the milestones: v1.1, v1.3 Apr 6, 2015
@dacap dacap self-assigned this Apr 6, 2015
@dacap
Copy link
Member

dacap commented Apr 9, 2015

Implemented in anticrash branch (it will be soon merged to master)

@dacap dacap closed this as completed Apr 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
critical priority feature Feature request, or something should be improved imported logic
Projects
None yet
Development

No branches or pull requests

2 participants