i don't know if this would be possible, but do you think it would be possible to have a xml editor for our dash's? i mean that would be really handy for working on a skin and such... or maybe just a text editor. but since i was check'n out avalaunch the other day, it has an irc client. and since alot of us who use mxm probley goto the irc chat, y don't we(i mean bj, mostly) look into encorperating it... just an idea(or actually a few)

Dingo

check this thread out...
http://forums.xbox-scene.com/index.php?act...T&f=58&t=160431

that version won't work for you unless you have a WIP version of MXM, but if i have time, i will convert it to a version you can use. just keep a look out in that thread.

And xml editing can be done through the 'treeview' element coming up for the new dialogs stuff.

interesting...

BJ, how's the current progress going?

QUOTE (geniusalz @ Jan 24 2004, 11:39 PM)

BJ, how's the current progress going?

I'm migrating ActionDraw lists (the collection of drawing commands used by the ActionScripts) and menus to be "SystemUIObjects" - basically, dialogs, menus, and draw lists will exist in a parent-child chain. I'm working out a few details here, and my menus will be XML based.

I may even have a way for action scripts to use the menu system.

ATM, Draw Lists are migrated, and seem to be working OK. Tomorrow I'll be working on getting the dialogs to be drawn (they are now a part of the "system" - but I spent time with the wife instead of fixing the rendering) and menus (menus have been placed into the internal XML)

It's slow going because there's a lot of underlying work. Until I start coding controls, there's very little visual payoff (hence, it's hard to get motivated working the hours I have lately). When I wrap up these two details, I will release an update for you guys to verify that nothing is seriously screwed up with the major changes.

On a side note, I will likely change the embedded variable spec.... changing them from [] to {}. I may do that on the WIP AFTER the next one, since I'd also like to get limited expression support in to make up for the abrupt change.

I had hoped to make a lot more progress, but work is in crunch mode. Our lead Japanese engineer has been here for two weeks, and I'd like to get things wrapped up THIS week so he can return home to his family (wife and newborn) - but we've been banging our heads because a software library vendor doesn't properly support a major feature they claim on their web site - and our customer requires we use this vendor's libraries!! Needless to say, we have the customer's rep to this vendor leaning heavily on them regarding this issue. This week doesn't look quite as bad, but there will be quite a few meetings to get these things resolved - which means I don't get much idle time I can spend on MXM

More venting

As long as there is progress, it's cool

I was looking at mIRC scripting recently, and noticed it is very similar to MXM's scripting. Was that the inspiration? I thought you said you didn't like IRC

Anyway, expression calculation is good, and drawlists (a.k.a. tweaking for tetris) are good too

Hope that situation at work clears up, so you can get time for more important stuff, like MXM

No, mIRC isn't an inspiration... DOS was.

BTW: I'm adding "MsgBox" as a formal command. It uses the System UI's MessageBox dialog class. It's also a test of a simple usage of a dialog. All of the app message boxes now use this dialog, too (like "About" and Game Info ).

I'm still working on porting over the menu into the system UI, the tough part being the handler that's pretty extensive at this point - but once it's done I can start working on individual controls.