At 23:17 24/11/2016 -0700, John Hart wrote:
I use an editor written twenty years ago for technical work. It automatically saves what you're working on every five minutes in a scratch file so if something goes wrong, you won't lose your changes.
You mean just like OpenOffice does? See Tools | Options... | Load/Save | General | Save | Save AutoRecovery Information every ... Minutes.
Another feature it has, when a file is changed, it automatically creates a backup, so even if the scratch file gets corrupted, the original isn't wiped out.
You mean just like OpenOffice does? See Tools | Options... | Load/Save | General | Save | Always create a backup copy, as well as Tools | Options... | OpenOffice | Paths | Backups.
These are simple things to implement, and with millions of OO users, would save a lot of people a lot of grief.
They would - and they already do! You can implement things, but you cannot force people to learn about the software - to read the help text or the documentation or to experiment with settings so that they actually know the facilities are there.
A feature to protect user files could be added in less time than has been spent chastising users for not learning how to do backups.
I'm sure implementing the facilities actually took far longer than it took you to complain - falsely - that they are not there, in fact. But it was done nevertheless. And you cannot write into an application such as OpenOffice total protection against user error, hardware faults, or operating system glitches.
You don't help others by broadcasting false information: you merely show your unfamiliarity with the product.
Brian Barker
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@openoffice.apache.org For additional commands, e-mail: users-h...@openoffice.apache.org
