Function
2010-01-19 19:44:18
I don't know if this has been suggested or not, but how hard would it be to make something so if you have any changes made and Simba shuts down un-expectidly (sp?) that you can have the option to restore that last session when you open up Simba next. I my no means have the programming experience to make this so I don't know how hard it would be. But I just thought of this cause I accidently closed Simba :duh:
The Claw
2010-01-19 19:47:44
Just log all open work to a file, load from that file at startup if the option is enabled? Should be pretty easy and useful.
Wizzup?
2010-01-20 04:01:04
I've been wanting to implement this, but there are a few practical problems. What if you have multiple Simbas open; will you only save the last one open?
There also needs to be a small tab rewrite before we get to this, but I definitely plan to add it.
mixster
2010-01-20 08:59:48
well, how about if you make it so that it stores all of the "backups" in a folder. Then, if it's saved (or if it's closed without saving them), the backup is removed. Then, when it starts, it reads that folder - any files in it can be presumed to be from Simba crashing unexpectedly of the like.
Wizzup?
2010-01-20 12:50:41
From: mixster
well, how about if you make it so that it stores all of the "backups" in a folder. Then, if it's saved (or if it's closed without saving them), the backup is removed. Then, when it starts, it reads that folder - any files in it can be presumed to be from Simba crashing unexpectedly of the like.
Making backups isn't the same as saving sessions though. :)
mixster
2010-01-20 13:04:09
s/backup(s)*/session file\1/g
- a session would have to be able to be stored somehow anyway, my main suggestion was just storing it in one place then reading that place to find 'lost' data regardless of how many Simba's are open or the like.