On Fri, Aug 10, 2007 at 09:15:30PM +0200, Mattias Gaertner wrote:
> > > For example GetValue('connectivity/answer_timeout/tag',2) will
> > > return 1000 instead of 2.
> >
> > Only if there is a nodevalue. But yes, that could be a problem.
>
> It is, because there is no function to change this value in TXMLConfig.
> The main purpose of TXMLConfig is to get and set some config values,
> not to parse an XML document.
The question was more (since I'm not to deep into XML), if there was a true
notation to linearise this. IOW if some character is used to signal
nodevalue, or simply #text or so.
> > I'm no XML wizard, which is why I actually reused code instead of
> > writing my own ( :-))
> >
> > So what would be (a) more normal rule to distinguish child values from
> > attributes?
>
> The Document property gives full access to the internal XML.
> I made the FindNode method public, so you can find the node easier.
I can't do much with this, since laz_xmlcfg (and the value=path) assumption
is a bit too deep into my framework at work, and this is only an exception.
But that is not a problem, I keep my "hacky" way, and don't merge it back.
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
