> Wouldn't it be a better idea to save to a new temporary file then copy that over the old file.
It already does that. It saves to myfile.capx.tmp, then providing everything has saved OK so far, it deletes the .capx and renames the .capx.tmp to .capx. So I have no idea how anyone could get corrupt files. I guess these things just happen, so hopefully autobackup will help there anyway.
(For the record it does the same for every file in a project folder as well - e.g. first it saves to Layout1.xml.tmp, then if successful it deletes Layout1.xml and renames the .tmp)
Considering this, it's indeed extremely strange someone could get a corrupted file. Dropbox auto-back up would be a great idea and maybe a web-disk option for those with their own server?