Leyart / aseprite

Automatically exported from code.google.com/p/aseprite
0 stars 0 forks source link

Data recovery (src/app/data_recovery.cpp) #381

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What do you need to do?
Avoid data loss in case of a crash.

How would you like to do it?
In case of crash it would be great to automatically see the program start again 
and restoring the previous state.

Notes for the developer: We need another process to watch the original Aseprite 
process. Aseprite and this "crash watcher" process should communicate through 
IPC (e.g. libuv + msgpack). Aseprite should send packages to the crash watcher 
of all actions done to sprites, and all pixel data that cannot be restored from 
the hard disk. When the communication is lost (the watcher sees that the 
Aseprite process doesn't exist and didn't receive a "terminate" message) the 
watcher should re-launch Aseprite and send back all packages that can 
reconstruct the "crash state" (or seconds before the crash).

Original issue reported on code.google.com by davidcapello on 30 Mar 2014 at 3:43

GoogleCodeExporter commented 9 years ago

Original comment by davidcapello on 10 Apr 2014 at 1:05

GoogleCodeExporter commented 9 years ago

Original comment by davidcapello on 10 Apr 2014 at 1:09