Print

[takamine]

What was posted?

[BenJeremy]

I think google is a bit dubious... there haven't been a lot of posts directly regarding MXM on 'regular' usenet.

There are only two posts it has directly mentioning "MXM" - one is a readme I mistakenly posted to a non-binaries group, the other an italian post that mentions MXM in passing as a possible dashboard.

[StrongBad]

BJ, the current MXM.xml type definition requires that each menu item element requires a number, eg <item_3>.  This creates a clerical headache when having to add an item near the top of the list to keep the menu, in my case, of 50 items in alphabetical order.  I have to rename each item to reflect a new item number.  Would it be at all possible to modify the type definition in a new version of MXM to accept the item element just as <item> instead of <item_#> and let your program determine the order of the menu list according to the order of the item elements within the xml?  That way, new items can be rearranged at will without having to modify the others.

Your thoughts?  Is this in the works in a new version?

[BenJeremy]

QUOTE (StrongBad @ Feb 27 2003, 11:26 AM)

BJ, the current MXM.xml type definition requires that each menu item element requires a number, eg <item_3>.  This creates a clerical headache when having to add an item near the top of the list to keep the menu, in my case, of 50 items in alphabetical order.  I have to rename each item to reflect a new item number.  Would it be at all possible to modify the type definition in a new version of MXM to accept the item element just as <item> instead of <item_#> and let your program determine the order of the menu list according to the order of the item elements within the xml?  That way, new items can be rearranged at will without having to modify the others. Your thoughts?  Is this in the works in a new version?

Actually yes... I am working to eliminate that (well, to allow you to leave off the number, at least) and use a true XML parsed configuration.

At the moment, it uses an XML parser that feeds a data structure similar to INI configuration (kind of an emulation). I've already done a bit of work to change that in writing the menu system to handle multi-level menus (though neither is done yet)

[StrongBad]

Sweet.. I can't wait to see the next update.  Total menu customization is so awesome.

By the way, did you get a chance to check out that skin?  If it still needs works, and isn't up to your expectations, pm me the details.

Cheers.

[BenJeremy]

QUOTE (StrongBad @ Feb 27 2003, 01:04 PM)

Sweet.. I can't wait to see the next update.  Total menu customization is so awesome. By the way, did you get a chance to check out that skin?  If it still needs works, and isn't up to your expectations, pm me the details. Cheers.

I'll pump it on my dev machine tonight, probably.... looks good from the video though.

The shaking text gave me a great idea for adding 'modifiers' to skin elements to do 'tremors' and such to X, Y, height and width attributes and such. I don't know what I'll be able to throw in the next release, but if I can, there is going to be some wild variations you can use.

[ray12944]

Just wondering if theres a way to change the scroll speed

appreciate it


keep up the good work    MXM Rules!!!!!

[BenJeremy]

QUOTE (ray12944 @ Feb 27 2003, 08:53 PM)

One more thing   Just wondering if theres a way to change the scroll speed appreciate it keep up the good work    MXM Rules!!!!!

No.... though I suppose that's something I could add to the new menus I'll be preparing for the generic skins.