[fpc-devel] Rather large flaw in TJSONConfig component

Mattias Gaertner nc-gaertnma at netcologne.de
Mon Jun 21 16:31:14 CEST 2010


On Mon, 21 Jun 2010 16:17:32 +0200
Graeme Geldenhuys <graemeg.lists at gmail.com> wrote:

> [...Sorry, I think my first message's attachment was too big. This one
> is smaller...]
> 
> On 21/06/2010, Mattias Gaertner wrote:
> >
> > TXMLConfig reads by default the old config.
> > Unless you use the same paths, no value is lost.
> 
> 
> Op 2010-06-21 15:38, Mattias Gaertner het geskryf:
> > Unless you use the same paths, no value is lost.
> 
> Sorry Mattias, but you are wrong. TXMLConfig shows the exact same issue as
> TJSONConfig. Here is the output after the test run. I attached the
> xmlconfig test suite.
> 
> Test is simple:
>  - load form 1
>  - load form 2
>  - close form 1 > which saves settings
>  - close form 2 > which saves settings and overwrites everything.

Now I understand.
Yes, TXMLConfig has the same "design flaw" as
TStringList.LoadFromFile/SaveToFile.
It is strange how you get used to such flaws and think it is normal.


Mattias



More information about the fpc-devel mailing list