Lock file in the project folder is staying behind when it should be removed.

[arnehemingway]

Hi,
I use the novelWriter AppImage on multiple machines and they all point to a project on shared storage. Yesterday I updated one machine to 2.5 and worked on my project. Today, I opened that same project on another machine using 2.4.3 and received a warning about opening a project created with a newer version of novelWriter.

I chose "no", exited novelWriter in normal fashion, switched to the new AppImage and was presented with the "another instance is running" warning, showing the hostname and OS of the machine I was on and dated moments earlier.

I think that, when answering "no" to the first dialog above, the lock file should be removed from the project directory.

I realize that this is a very minor issue. I bring it to your attention more as a service to you than anything else.

[vkbo]

It could be the lockfile is created too early. I'll investigate.

[vkbo]

Yes, the lock file is created when the project session object is successfully initiated, but before a number of other checks, including the project format upgrade/downgrade checks. I've rewritten it so that the project is not lucked during initialisation, but after a completed project open process.