The following apply to data that can be any length, and there is no way to tell. (I hope you will get what I am talking about)
Num, from now on we make the program check what exactly is in the settings file , each "part" should have markers (incoded rubble that indicates what the settings file does or does not have.).
And this should happen if the settings file does not have any markers at all prompt: "Is it ok to convirt your old settings file into a newer settings file?"
Then if no , read it as the old one.
And this should happen if the settings file does have any new markers. prompt: "Is it ok to convirt your old settings file into a newer settings file?"
Then if no , read it as the settings file with the markers it has.
This way If we get a settings file with some new data missing, or we run a new settings file on a old virsion , we wont get any problems because the program will search for the markers before reading the settings.
The only problem is how to make it search? and then change the "get..." position.
Looks like we are going to load the whole think binary and then opperate on it, unless you know some commands I dont.
And the marker stuff must only apply to the new stuff because the old stuff must still work in the old DB pre 2.3 Db...
(although now that I think about it all above is not really nessisary If I just would of coded my stuff to the end of the file :banghead: )