3.6 Calc Problem / ~lock

users
#1

That ~lock pops up all the time whenever I used OO - and then LO -
       HOW can it be stopped?; is it a bug which has continued form day 1?;
it happens in all the OO/LO programs ;-(

       Each time it appears, I delete it; I would search through
'properties' for an option to stop this inane phenomenon, but never found
anything.

       Sure hope this bug will die anon.

Hi :slight_smile:

#2

Hi.
I think that ~lock is used to control access to the document you have open. To stop another user from changing it unless you have enabled multiple user access for simultaneous editing.

Usually it goes when you close the document, sometimes they stay after closing LO and I delete them.

Steve

#3

Hi :slight_smile:
+1
Usually it all works very smoothly and it's kinda nice to see the lock-file appear and vanish as if by magic.  Definitely a feature and NOT a bug, except when something else throws a spanner in the works
Regards from
Tom :slight_smile:

#4

Thank you for your reply.

       For you, developers - as for me, it sure would be nice to be able to
turn this inane phenomenon off -
           it seems to slow down the program :wink:

Hi.

#5

Thanks for your response -

       unfortunately, it does NOT go away;
           sometimes, I've found several of these ~lock files ;-(

Hi :slight_smile:

#6

Thanks for your response -

        unfortunately, it does NOT go away;
            sometimes, I've found several of these ~lock files ;-(

#7

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 :wink:
              and the more these machines change, the more I think I should
pitch them out the window and return to the 'horse & buggy' era :wink:

       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 ;-)]

#8

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 :slight_smile:

#9

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.

Hi :slight_smile:

#10

Hi :slight_smile:
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 :slight_smile: