Date: prev next · Thread: first prev next last
September 2015 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=94042

Cor Nouws <cno@nouenoff.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cno@nouenoff.nl

--- Comment #2 from Cor Nouws <cno@nouenoff.nl> ---
Hi Jay,

(In reply to Yousuf (Jay) Philips from comment #0)
It is always a problem when LO crashes that users will loose data and in
order to help reduce that large amount of lost data, i think we should
change the autorecovery from 15 minutes to 10.


Agree - easyHack..

We should also consider implementing a smart autorecovery algorithm that can
work within the set autorecovery time, so that if a user for example stops
[...]  So if a user is working on a small
document and save/autorecovery last took 3 seconds, we could smart
autorecovery save if a user hasnt done anything in 1 minute, while if a user
is working on a large spreadsheet that takes 30 seconds to
save/autorecovery, we could smart autorevoery save if a user hasnt done
anything in 5 minutes.

Agree - separate issue?

Also it would be useful to save a copy of the last autosaved document when a
user closing an application and says not to save the changes.

Agree - separate issue?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.