Originally Posted by Rasbats
How to avoid the opencpn.ini issue? I think any plugin will write some data into that file, even if it is only the name? And people may have multiple installations of OpenCPN. Setting up preferences without access to an ini file makes more work for the user. Suggestions?
It seems to me that you did not understand the fact that there is only one opencpn.ini file. Correct me if I'm wrong.
Suppose you have two instances OpenCPN which runs at the same time. When you stop one of them, it completely rewrites the ini file with settings. When you exit the second instance, it also rewrites its settings in the ini file. And if they do not have the same settings, the settings of the second overwrite the first. When you restart O, what are the settings of the last instance that you stopped serving. That is why we must avoid two simultaneous instances of OpenCPN.
By cons, you do not have this problem if one of the instances takes place on USB key (portable version) and if the other instance is on the hard
drive. In this case, there is an ini file on the hard
drive and an other ini file on the USB key.
Finally, it seems to me that the latest beta of OpenCPN, it is no longer possible to have two concurrent instances launched on the hard disk. There was a whole series of posts in a thread on this topic in the cruisers forum. And Dave was very clear about this.
Best regards. Gilletarom.