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
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.)
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
The text was updated successfully, but these errors were encountered: