On Fri, 14 Sep 2012 07:23:33 -0400 TJ Frazier <tjfraz...@cfl.rr.com> wrote:
> On 9/14/2012 05:52, RGB ES wrote: > > 2012/9/14 FR web forum <ooofo...@free.fr> > > > >> Hello, > >> > >>> I strongly suggest that an important alteration to all future releases of > >> AOO > >>> should be a file save protocol whereby at least a version of the file > >> being > >>> edited is saved as a backup file. > >> > >> See this issue: https://issues.apache.org/ooo/show_bug.cgi?id=111290 > >> > >> Another way will be to modify by default Options > Load/Save > General. > >> Always create backup copy should be checked and Save AutoRecovery take > >> too much time. It shouldn't be 15 min, but 2-3 minutes. > >> > > > > +1. But with a difference: those backup files are saved on the user profile > > folder. That user profile is hidden on all OSs and for most users a hidden > > folder means they will not be able to find the backup file without > > guidance. > > > > Regards > > Ricardo > > > Hi, folks, > > The changes you're suggesting would probably help. But what would help > more is fixing the !#$%* problem! I use Writer heavily, and since 2.0 I > have never seen this bug. However, I run with a big UPS, and *never* > have power failures. AOO should behave gracefully for those. There > should be some way to rig a VM to simulate a power failure for the o/s > (which is much easier on the hardware than testing with actual power > failures). Then maybe the devs can find and fix the bug. > > /tj/ > Most of the subscribers to ooo-dev and many of the other ooo lists are experienced computer users who use their computers with care. They would not ignore a laptop "low power" warning and most probably have a regular backup policy in place. Not so, unfortunately, the ordinary user, for whom the computer is a "magic box"; such a user doesn't know or care how it works, and doesn't understand that the "magic" has limits, especially when confronted by rank stupidity. I agree with tj - I have never seen this bug in five years of heavy Writer use, but as I say above, I'm an experienced user. But working on the en-Forum we regularly see such postings as the one referenced at the start of this thread; we need to protect such users from themselves. There will of course be corner cases where nothing can help (catastrophic HD failure, for example), but OpenOffice should cope with sudden power failure or computer crash, at least to preserving a print of the file in its last opened state. The problem is that a crash often erases the last opened state. It should not do this. -- Rory O'Farrell <ofarr...@iol.ie>
