Print

[flattspott]

This is what I'm getting;
<audioplayer enabled="1" path="C:\xboxdash.xbe">
</audioplayer>

and this is what I want;
<audioplayer enabled="1" path="C:\xboxdash.xbe"/>

[BenJeremy]

Well, there's not much that can be done about that at the moment.

It shouldn't affect anything.

[flattspott]

So avalaunch would still see them both the same? Cause that's what this is all about.

[BenJeremy]

QUOTE (flattspott @ Feb 10 2004, 01:01 PM)

So avalaunch would still see them both the same? Cause that's what this is all about.

It should.... but it depends on how they are parsing their XML.

I started with PD code that had a LOT of bugs, since fixed, and also put a lot of work into the tree access.

[flattspott]

Okay I' test it myself.

However I'm curious at to what the true arg does.

After looking at the internal.xml I saw you added that attr for the name (thanks for adding that btw). So that's what I used as an example for my newest script.

XMLSetValue avaXML !.network.setup "1" true gives me
<network setup="1">
</network>

Now what would it do if I left off the true arg or changed it to false?

Also another thing thing I'm wondering about is how this XML is made in relation to the XAS file. Cause in my script I have them one order then in the produced XML they are in another

XMLSetValue avaXML !.user.irc.font.name "framd" true
XMLSetValue avaXML !.user.irc.font.size "12" true
XMLSetValue avaXML !.user.irc.server irc.homelien.no
XMLSetValue avaXML !.user.irc.nick woo484
XMLSetValue avaXML !.user.irc.altnick _USER2_

Makes this below, with the fonr part at the bottom, even though i thought it was gonna be fisrt.

<irc>
<server>irc.homelien.no</server>
<nick>woo484</nick>
<altnick>_USER2_</altnick>
<font name="framd" size="12">
</font>
</irc>

[flattspott]

And while I'm at it, how about an XMLComment command?

[BenJeremy]

QUOTE (flattspott @ Feb 10 2004, 01:29 PM)

And while I'm at it, how about an XMLComment command?

Well, to understand how XML works in MXM, you have to know that I track things in a "tree" - nodes are different from elements. When writing out the XML from this tree, elements are obviously (from your example) dumped first, then nodes. These are two distinct groups of items.

As for comments, it would require quite a bit of work for me to do that at the moment. Suffice it to say, I'd like to revisit the XML stuff at a later time and re-write some things, but I don't want to break anything, and currently, most of my energy is in getting the System UI stuff done for the next release.

As they say "if it ain't broke, don't fix it"    While I'd like to redo some aspects of the XML system, there's no pressing need (from MXM's perspective) at the moment to mess with it.

[flattspott]

[flattspott]

One more thing.

Damn, this XML/actionscript parsing or whatever is fast. It spits out an entirely new avalaunch.xml in less than a second.

Way to go