To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=110399





------- Additional comments from [email protected] Fri Mar 26 21:39:47 
+0000 2010 -------
@es: I don't see a way to reproduce the crash (most of my crashes happen in 
different circumstances). And this was the first case that the recovery was not 
satisfactory (so my vigilance was relaxed).
I suggest to display different messages in two distinct situations:

- if OOo has completed autosave before the crash and is using so saved files 
for the recovery, then these files are reliable (except that results of a few 
minutes of the user's work are lost) - in this case the message (forgive me, if 
the following translation from Polish does not precisely match the English 
message) "The files were restored correctly" is fully justified.

- if OOo tries to save the files AFTER detecting troubles (like it was in my 
case), then perhaps there is a danger of unreliable saving. In this case the 
user should be effectively warned (e.g. with big red letters) that he/she 
should verify the file (this corresponds to mav's post, above). This message 
should also present a way, in which (after a negative verification of some 
files) the user could make a use of previous, correctly autosaved versions of 
selected files. Of course if a file was manually saved *after* its last 
autosave, the user should be informed about that.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to