Revision backups

LineCutter · #1 (**permalink**) 06-02-2007, 12:30 PM

With the autosave feature (& without it too) it's quite easy to write a chunk of code, test it & decide you wanted to go in a different direction... but you forgot to save a version of the file before the branch.

It would be nice to have auto renaming of the current .sbp file (adding to date to the filename?) to provide auto-backups. Some kind of backup directory & housekeeping functions for number/age of backup files might be nice, but I'd be prepared to tidy up myself if these simply triggered a warning msgbox.

Cableguy · #2 (**permalink**) 06-02-2007, 02:58 PM

Yes I tend to agree that it would be usefull if atleat the currently in use file would be backed up during its editing time.
What i mean is that some time I stop programing when i reach a surtain run capability, and the resume coding... At that time if any of my current coding errors,and since some features demand previous save, i'm stuck with an erroing app.
My sugestion would go in to making auto-save actually auto-backup, and only when we closed the file or finished currrent coding session, prompt to save/update the sbp file...

bdiscount · #3 (**permalink**) 06-02-2007, 03:21 PM

I think that this would take a lot of time as I run as I am coding.

Cableguy · #4 (**permalink**) 06-02-2007, 03:46 PM

There would be no noticeable loss of time as normally we have the auto-save feature on, but imagine an app tha has 10 of 20 subs, you tned to go by stages and do specific event driven subs before any "calculations" subs, at least I do....So if after all the event sub were done if you had an error in a "calculations" sub that you just couldn't see", a backup file would be of interest in order to restart Exactly from where you were, and re-think the troubling sub...
I've had ocasions when it was easier to me to just restart the hole project because I just didn't know anymore what subs worked and were could be my eror...If only I had Backed up that time....Of course we can alway do our own back-up before re-opening a sbp file, if we remember to...

bdiscount · #5 (**permalink**) 06-03-2007, 09:57 PM

The idea would be to saveas before testing new code if ok then saveas original. Otherwise you need multi bak files. To make a bak files you have to rename the old and save the new, which as I said would take time.

LineCutter · #6 (**permalink**) 06-04-2007, 08:23 PM

My view:
On running the working program you have autosave set to on & save the current project over itself.
Changing this behaviour to autosave the current project under a different file name should take the same time, but will use disc space. This could be tidied up/prompted for at the close of the editor.

With this "autosave as backup" as an option, everyone should be happy.

bdiscount · #7 (**permalink**) 06-05-2007, 01:26 PM

Linecutter has a good method. it would use a lot of dick space but would be retrievable. I do save as if i plan a diff route.

LineCutter · #8 (**permalink**) 06-05-2007, 10:27 PM

Quote:

Originally Posted by bdiscount

Linecutter has a good method.

An option to keep n autosaves in total, where n is user configurable, would solve the problem. 25-50 would cover the sort of slip ups I've created for myself.

Quote:

Originally Posted by bdiscount

it would use a lot of dick space but would be retrievable.

PMSL