New sign-ups are no longer accepted here. Although existing users can sign-in and create posts, we request that you please join us on Discord and initiate/continue conversations there.
Lock file

Quote from SHRIDHARA K S on December 9, 2021, 9:39 amalways Lock file disturb working speed its generating within some minute we go to folder and we have to delete the file then only its start access to work.
always Lock file disturb working speed its generating within some minute we go to folder and we have to delete the file then only its start access to work.

Quote from TERIFLIX on December 9, 2021, 9:49 am@shridhar-ks: The lock file is meant for solving an compelling problem. Please read this to know more: https://www.scrite.io/index.php/sync-scrite-documents-across-windows-macos-and-linux-desktops/
The way lock file works is like this:
- Open a file in Scrite, lock file gets created.
- Close the file in Scrite, lock file gets deleted.
Some of our users share their Scrite files on Google Drive, One Drive etc with other writers who collaborate with them. For them,
- When the first writer opens a file in Scrite, lock file gets created.
- Collaborator opens the same file, gets notified that file is locked.
While you can manually delete the .lock file, its a simple co-operative mechanism to ensure that two writers (or two instances) don't end up overwriting a file.
Sometimes if Scrite is gets terminated (maybe because the app crashed or for any other reason), the .lock file will remain on the disk. In such cases, you can simply delete the lock file and reopen the document.
@shridhar-ks: The lock file is meant for solving an compelling problem. Please read this to know more: https://www.scrite.io/index.php/sync-scrite-documents-across-windows-macos-and-linux-desktops/
The way lock file works is like this:
- Open a file in Scrite, lock file gets created.
- Close the file in Scrite, lock file gets deleted.
Some of our users share their Scrite files on Google Drive, One Drive etc with other writers who collaborate with them. For them,
- When the first writer opens a file in Scrite, lock file gets created.
- Collaborator opens the same file, gets notified that file is locked.
While you can manually delete the .lock file, its a simple co-operative mechanism to ensure that two writers (or two instances) don't end up overwriting a file.
Sometimes if Scrite is gets terminated (maybe because the app crashed or for any other reason), the .lock file will remain on the disk. In such cases, you can simply delete the lock file and reopen the document.

Quote from Prashanth Udupa on December 15, 2021, 11:33 am@shridhar-ks: Any update on this? Did the pointers help?
@shridhar-ks: Any update on this? Did the pointers help?

Quote from SHRIDHARA K S on December 15, 2021, 3:03 pmI understood the process. and Its useful thank you
I understood the process. and Its useful thank you