Ok, 2 scenarios.
1. A desperately slow machine (probably Windows). Double-clicking a file
doesn't seem to open it, not entirely convinced it was a proper
double-click so double-click again. At last it opens and you make a lot of
changes, and go off to grab a cuppa tea. back at the computer you are not
sure if you saved the document and even tho your fairly sure you closed it
it still seems to be open so you save again and quit. Later you open the
document to find NONE of your changes have been saved. Why?
2. On a swift machine with multiple workspaces you want 2 copies of the
file open, one to edit and the other on a different workspace to copy info
from or as a look-up source. After a ton of editing you get a phone call
and switch workspaces to look-up stuff from various open files to deal with
the call. A few distractions later and you get back to the machine and
save and close the open document and shut-down the machine. Next day you
find NONE of your edits were saved. Why?
I'm sure you can imagine a ton of situations where something could easily
occur in your own place where you might not be 100% focused and infallible
on an infallible machine.
Regards from
Tom :)
From: anne-ology <laginnis@gmail.com>
Subject: Re: Re: [libreoffice-users] Re: 3.6 Calc Problem / ~lock
To: "MiguelAngel" <mariosv@miguelangel.mobi>
Cc: users@global.libreoffice.org
Date: Thursday, 30 August, 2012, 3:17
Huh ???
Well, (1) these ~lock files do appear when the file is open -
that's what's frustrating; when it begins to slow
down, I check & discover this inane file has appeared.
(2) I do NOT understand why I should place the file away from the
computer's HD before its completed?;
once completed I copy it to an external HD, but still retain
it on the computer's HD.
(3) I do NOT understand why I, the sole user of this machine, would
not have access to do whatever I wish with this machine ;-)
and the more these machines change, the more I think I should
pitch them out the window and return to the 'horse & buggy' era ;-)
A bug or not a bug ... a bug by any other name would be the same ...
which reminds me of these silly acronyms - there were wasps -
still are - flitting around the woods ... then there were WASPs following
the AAC in WWII ... then there were WASPs - according to the '60s media -
along with other groups back-then.
[and that's just 1 example of how acronyms can become confusing
;-)]
On Wed, Aug 29, 2012 at 7:05 PM, MiguelAngel <mariosv@miguelangel.mobi
wrote:
Asunto: Re: [libreoffice-users] Re: 3.6 Calc Problem / ~lock
Fecha: Wed, 29 Aug 2012 18:23:17 -0500
De: anne-ology <laginnis@gmail.com>
A: Tom <tomdavies04@yahoo.co.uk>
CC: Steve <steve.edmonds@ptglobal.com>, users@global.libreoffice.org
Thanks for your response -
unfortunately, it does NOT go away;
sometimes, I've found several of these ~lock files ;-(
------------------------------**------
I've only seen this issue when the file is not closed properly.
For example remove the memory stick with files opened.
A program crash.
Or maybe do not have rights to delete in that directory.