-
is there a way to disable this feature? I work on a couple of different computers during a typical week (sharing an office with my wife, there are times I cant work there) and I end up deleting .lock files and conflicted Project files just to access a Project. I am worried about the stability of novelWriter with the way I treat it. Please advise |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
It's a safety feature to prevent you from overwriting your own data, but you can click yes to ignore the warning and continue, which should force novelWriter to proceed as normal. Ideally, you should close the project on one computer before opening on another. In the end, the warning is just a warning, and the lock file only exists to provide that warning. It is there for a reason, but selecting to override it has no other consequences for the functionality of the application. The only real risk of data loss is if you have the same text file within a project open in both places and have made different changes to it on each computer. The two versions of the file will just overwrite each other and the last one to be closed will get the last word. If you have file sync software, it may register the conflict and mark the files as conflicting in such cases. These are the files in the The lesser risk is that if you add a new file to the project on one end, the other one will not know about it until the next time the project is opened (it scans everything when you open a project). It may then find "orphaned files", which will lack some of the settings you may have picked for it. However, the content of the file will be fine. Files found this way will be re-introduced into the project, and marked so you know it has been recovered. novelWriter will do its best to put it in the correct place, but you may have to make the final decisions. This is a case of diverging A non-critical risk is that your project index may also drift out of sync, which means your word counts may be wrong and tags made on one computer may not be known on the other. But all of that can be fixed by pressing At the end of the day, novelWriter works with human readable text files for a reason. It makes it less vulnerable to project-wide file conflicts and easier for file sync software to deal with. I am considering adding a few more safety features to prevent overwriting conflicting files like may occur in this type of cases, but it will not resolve the issue with diverging project files. |
Beta Was this translation helpful? Give feedback.
It's a safety feature to prevent you from overwriting your own data, but you can click yes to ignore the warning and continue, which should force novelWriter to proceed as normal. Ideally, you should close the project on one computer before opening on another. In the end, the warning is just a warning, and the lock file only exists to provide that warning. It is there for a reason, but selecting to override it has no other consequences for the functionality of the application.
The only real risk of data loss is if you have the same text file within a project open in both places and have made different changes to it on each computer. The two versions of the file will just overwrite each ot…