Hi :) The point was that if you open the same document twice and make tons of changes to 1 version but then for some reason end up saving the 2nd copy and not the one you edited then you lose all your changes.
Even if there is only 1 person using the system the chances are still quite high of such a thing occuring and so OOo developed a way around it. It rarely goes wrong and if/when it does it's easy to fix and doesn't result in a loss of data. Not having a ~lock file would often result in a loss of data if a problem occurred. Regards from Tom :) >________________________________ > From: anne-ology <[email protected]> >To: Tom <[email protected]> >Cc: [email protected] >Sent: Thursday, 30 August 2012, 15:29 >Subject: Re: Re: [libreoffice-users] Re: 3.6 Calc Problem / ~lock > > HUH ??? > > Whenever the document is saved, it's saved ... when the file(s) are >re-opened the saved document appears; > if it's been saved with a different name - as adding 2 ... - then >there are more than 1 copy of this document. > > > > >On Thu, Aug 30, 2012 at 4:45 AM, Tom Davies <[email protected]> wrote: > >Hi :) >> 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 <[email protected]> >> Subject: Re: Re: [libreoffice-users] Re: 3.6 Calc Problem / ~lock >> To: "MiguelAngel" <[email protected]> >> Cc: [email protected] >> 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 <[email protected] >> >wrote: >> >> >> > Asunto: Re: [libreoffice-users] Re: 3.6 Calc Problem / ~lock >> > Fecha: Wed, 29 Aug 2012 18:23:17 -0500 >> > De: anne-ology <[email protected]> >> > A: Tom <[email protected]> >> > CC: Steve <[email protected]>, [email protected] >> > >> > >> > 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. >> > >> > >-- >For unsubscribe instructions e-mail to: [email protected] >Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ >Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette >List archive: http://listarchives.libreoffice.org/global/users/ >All messages sent to this list will be publicly archived and cannot be deleted > > > > -- For unsubscribe instructions e-mail to: [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
