Print

[DeVante]

CODE

XBOX Menu            Powered by MXM            True            False            C:\MxM\skins            BlackBox            True

... the skins path won't work.

However; if I load the MXM.XML like this:

CODE

XBOX Menu            Powered by MXM            True            False        C:\MxM\skins        BlackBox            True

... everything works fine. Notice the difference in the format of the skins tag.

Why exactly is this?

Note; these are only exerpts of my whole MXM.XML file.

[BenJeremy]

That's because there is a difference between "C:\MxM\skins" and "
C:\MxM\skins
"

(Linefeed/carriage returns)

There are times when the "white space" is desired, and times when it's not.

I'm fixing most of those issues, however, with the latest release, on my end - just to avoid the confusion.

[DeVante]

CODE

True

... as opposed to this?

CODE

True

Or does every tag need to be formatted so that it does not have carriage returns?

[BenJeremy]

QUOTE (DeVante @ Sep 24 2003, 07:06 PM)

Sounds awesome. I'm just glad I decided to use MxM in the first place. As I'm still fairly new to XBOX modding, I don't understand how anyone can prefer any other dash over it (well, unless you like hacked MS dashes which is understandable). Anyway, back on topic, does this "carriage return rule" apply to tags with definitions that aren't pathnames? For instance, would this work? CODE True ... as opposed to this? CODE True Or does every tag need to be formatted so that it does not have carriage returns?

In some cases, where I am looking for a true/false, or a number, I created a "GetBool()" or "GetLong()" function that trims off the whitespace automatically.

The "GetString()" doesn't, by default, but it has a parameter I can set to force it to.... that's what I've done in the code for the next version.