Issue 99615 - Show an error if something goes wrong during autosave.
Summary: Show an error if something goes wrong during autosave.
Status: ACCEPTED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: All All
: P2 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-25 10:30 UTC by aviret
Modified: 2017-05-20 10:48 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description aviret 2009-02-25 10:30:46 UTC 
Hi Mikhail,

Checks that the autosave has not generated an empty file and warn the user when that's the case.
This has to be activable (default)/deactivable (in the xml config file is sufficient, UI not needed).

Related to the issue 83352 / Case 38224321.

Greetings,
 Alain
Comment 1 mikhail.voytenko 2009-02-25 10:40:03 UTC 
Setting the target release to OOo3.2.
The autosave implementation should show a warning in case autosave have a
problem ( that usually triggers empty file generation ).

Necessity to deactivate the warning depends from the mechanics that is used to
show it. With the current design the ability to deactivate the warning is
necessary, since the error-messages are modal dialogs.
Comment 2 mikhail.voytenko 2009-03-30 15:17:10 UTC 
Changing the Summary.

mav->fl: The problem could happen during auto-save action, that means that the
document would be probably inactive at this point of time. There looks to be two
possibilities to show the error currently:
1) Show a kind of docking window that contains the warning and can wait until
the user returns to this window. Would need a completely new design.
2) Show an error message in the standard dialog, that will definitive disturb
the user in case he edit a different document. For this reason we need probably
an additional checkbox "Do not show the message for this editing session any
more" or something like that.

Although the first solution would need a completely new design it looks to be
more reasonable in this case. Actually it should not be a problem to implement
something like this. Would you be able to design this docking error-message
window for 3.2? If you like, I could prepare a prototype for this.
Comment 3 frank.loehmann 2009-04-30 16:13:18 UTC 
Project Renaissance, to create a new UI for OOo, is currently running. A general
mechanism to show non modal warnings and errors will be part of the UI concept.
So we should wait for this new framework to create a warning for this issue and
not implementing something that will may be obsolete soon. Showing a modal
message box is no solution in this case. -> changed target to 3.x.

Furthermore this message makes only sense if the user could change something
like to free some disk space to make this function work again. Errors like
i83352 should be made reproduceable to fix the cause and not on symptoms.
Comment 4 Marcus 2017-05-20 10:48:15 UTC 
Reset assigne to the default "issues@openoffice.apache.org".