This content has been marked as final. Show 2 replies
Hmm, I see now that rather than manage multiple xml nodes, flex prefers to group similar nodes into a single array.I'm not particularly fond of this as it goes against how I work with XML in other languages and platforms, but I can live with it for now.
As a workaround, I'm removing duplicate nodes and instead appending children to the same children over and over again. So the result now looks like this:
In action script, I have to do the following to access those text nodes:
I guess this isn't to bad. Had it worked my way, the only difference would have been:
So there's an extra step involved. Perhaps I'll just write a wrapper that will do this for me.
If anyone wants to share their comments on this, please do. Meanwhile I'm going to label this topic answered.
"TheNut007" <email@example.com> wrote in message
> Hmm, I see now that rather than manage multiple xml nodes, flex prefers to
> group similar nodes into a single array.I'm not particularly fond of this
> as it
> goes against how I work with XML in other languages and platforms, but I
> live with it for now.
You didn't really say how you were getting your XML that you were looping
through, but I did suspect you had an XMLList instead of a single XML node.
But without more information, it wasn't really possible to give a good
answer to your question. Flex's implementation of e4x is pretty much the
same as e4x in any language or platform.