<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - FILESAVE: Auto save timing logic problem: can save too frequently"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=122530#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - FILESAVE: Auto save timing logic problem: can save too frequently"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=122530">bug 122530</a>
from <span class="vcard"><a class="email" href="mailto:luke.kendall@gmail.com" title="Luke Kendall <luke.kendall@gmail.com>"> <span class="fn">Luke Kendall</span></a>
</span></b>
<pre>I assume this comment is a little misleading:
"// force save of all currently open documents"
I assume it really means "force save of all currently open documents that have
been modified".
Even so, if the design really is that autosave triggers and saves all documents
at the same time, that seems wrong to me if it really means the more documents
you have open and are working on, the more likely autosave is to trigger.
I'm not a C++ programmer, and I'm afraid I couldn't follow the logic. I
couldn't even work out the start point from which the time period is measured.
I get the idea it's measured from a fixed time (e.g., when Writer started
running?), and is not related to the elapsed time since a document was last
saved? That seems wrong.
>From this user's perspective, the autosave period seems like it's a way of
choosing "How many minutes of work on a document do I want to risk losing if LO
crashes?"
If the time isn't measured from a document's last 'safe point' (so, the maximum
of last save time, and when the doc was opened), then I don't have any idea
what it means. If it isn't measured from each doc's last 'safe time', then the
user can't avoid being interrupted even if they're diligent about saving
regularly.
I think implementing the request of <a class="bz_bug_link
bz_status_NEW "
title="NEW - Put every application in different CPU process"
href="show_bug.cgi?id=63554">bug 63554</a> would solve the problem. The
person asked for each document to be a separate process, not a separate thread.
Separate processes don't share memory as far as I understand things. At least,
not memory used for data.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>