Whatever

"Zak McKracken" <[email protected]>
Newsgroups gmane.comp.openoffice.general
Message-ID <[email protected]>
OK, since everyone agrees that the OP was not quite as polite as would  
have been appropriate, let's be serious:

I've been having issues with OO' restore function, too. Regularly, if I'm  
working on something, saving, working on something else until OO crashes,  
it will restore the saved document to a version that is older than the one  
I have saved half an hour ago. => It would be coole if OO could check the  
date of the backup-save (I've set to do that every ten minutes, but I  
guess it only does that while I'm actually doing something to the  
document), compare to the latest manually saved version and give me that  
if it's younger.

In another case, I was writing a work protocol as I went along, i.e. I had  
the same (draw) document open for weeks and sometimes just typed a word or  
two, then continued doing something else, not always remembering to save.  
Eventually the computer did crash (not OO in this case), but upon  
restarting OO, it also offered to restore to a much older version, so,  
because I didn't realize the error immediately, I lost some part of that  
protocol, because I saved the older restored version over the saved one.

=> As with many crash-related things, I can't really file a proper bug  
report or reproduce the behaviour properly, but by now I've switched to  
always making a manual backup of a saved file that OO is offering to  
restore after a crash, then compare carefully, then decide which version  
to use. Maybe someone who knows more about the inner workings of this  
mechanism can say something smart on it?

Of course I am making backups of the really improtant stuff, but I'd  
appreciate if the crash recovery wouldn't add to the reasons for doing  
that. (Alright, most of the time it does work properly, but that's not the  
times I remember best...)

Zak
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.