Comment 23 for bug 679917

Thomas, I'm a Unix-guy. Apparently you're not. I have to depend on you to make suggestions as to usable names on Windows, and on where to look in the source code on how to do it. Please make a suggestion, besides telling me that "$HOME/...." sounds unix-y. I already know that.

As I see it, having 10 backup project files around is acceptable. Deleting them when hugin exits succesfully negates part of the "having a backup". (We of course got into this because "hugin crashes", but a backup can also protect against: "I had it linedup just fine yesterday, and now I can't get it to line up correctly! aargh!". For this last situation, removing the file on succesful exit is not desirable).

Using a "random name" means we can't leave them lying around, because there might end up lots of them.

On Unix, if you open a file, and then rename (or delete) the file, it will remain linked to the file you originally opened.

I find "the backup of the first instance of hugin disappears if I open 11 instances of hugin" an acceptable compromise between disk space and usability. (you'll have up to five backups if you don't open more than two hugin instances at the same time). A preference setting may be implemented for this as well. 10 is not a magic number.

the electronics design software "eagle" keeps old versions of your design around as backups with a number. Every time you save, it moves the previous versions up one number. This way you have up to 10 backups of your project should something go wrong.

How about: We save under the "normal" name, with: '.0" attached for the autosave. When an explicit save comes about, we remove .9, move .8 to .9, .7 to .8 etc, and then save under the given name. (before naming your project, the autosave will be in "unnamed.pto.0")

Current patch attached. I didn't manage to get the start-rev right, so I manually removed the other stuff. On the other hand, I hadn't tried "hg view" yet, which I have yet to learn how to use. :-)