File-lock II

The previous topic was closed, so here my last words about it, because there are zillions of technical misunderstandings.

I do not mean a physical file lock (I am a software engineer but an author also) or any other problem that could have to do with it, I mean a simple virtual lock, a switch that has nothing to do with a file locking mechanism or in-memory topics. If you lock it in the app, for example by reading an attribute, lock the editing globally with a shared-memory-lock attribute that’s it. It does not affect any reading mechanisms, writing mechanisms, file locks or file attributes.
It would be very useful and I am sorry if you are ignoring it. That’s all. Now you cn close me again/delete me whatever

The previous topic was closed for the same reason this one will be. Thread duplication is frowned upon, independent of the merits of the topic. If you’d like to comment further, you are welcome to do so in the (still open) pre-existing thread.

1 Like

Just for clarification on this, the previous thread wasn’t closed as such, but the posts were merged into a larger thread to better manage the discussion (easier to follow one thread than scattered posts). Any further conversation should just be in that main thread, where your post now resides with some responses. :slight_smile:

2 Likes