It's definitely not LETGui that I had in mind when I was writing that lines!
I can not see this problem. Given the following situation:
That file is already in place. Someone created a new application. Let's say LDFind. The Author like to give you as the user the possibility to open the file found with MLCad. With the new file he just needs to read the entries in that file for MLCad entry and use the found value. If nothing is found the author can not show you the button to use MLCad.
On the first start of LDFind it will open the file for reading (is my own entry in the file) if not the file is opened for writing and the value for LDFind is written to the file. I can not really imagine that two application at the same time are doing that.
Code:
Dangerous. If two or more apps attempt to access the file simultaneously and one of them is writing to it then - at best - the others won't see what they need to, and if more than one app is writing to the file then there will be data-loss and/or corruption.I can not see this problem. Given the following situation:
That file is already in place. Someone created a new application. Let's say LDFind. The Author like to give you as the user the possibility to open the file found with MLCad. With the new file he just needs to read the entries in that file for MLCad entry and use the found value. If nothing is found the author can not show you the button to use MLCad.
On the first start of LDFind it will open the file for reading (is my own entry in the file) if not the file is opened for writing and the value for LDFind is written to the file. I can not really imagine that two application at the same time are doing that.