I'm not being negative just practical...
Well personally I prefer the regular formatted INI file and I'll tell you why.
My screen savers have a configuration component written in VB and it reads and writes to the INI file using the standards Windows API calls. Now a custom INI file would require loads more programming on the VB side.
Perhaps your new INI format has advantages over the standard MS one but IMHO the last thing we need is different formatted INI files. In fact I would go one step further and say don't give yours a .INI extension as it's NOT an INI file.
Well personally I prefer the regular formatted INI file and I'll tell you why.
My screen savers have a configuration component written in VB and it reads and writes to the INI file using the standards Windows API calls. Now a custom INI file would require loads more programming on the VB side.
Perhaps your new INI format has advantages over the standard MS one but IMHO the last thing we need is different formatted INI files. In fact I would go one step further and say don't give yours a .INI extension as it's NOT an INI file.