Reloading the menu.xml while MXM is running is not needed. The way I have the script now, when you launch a game, it first edits the menu.xml file to reflect that this game has been launched recently, then it actually launches the game. When you've finished playing, you reboot to MXM and it loads up the modified menu.xml.
What I'm trying to avoid is the possibility of the script failing and corrupting the entire menu.xml. I'd like the script to instead edit a secondary xml file, which would then be "included" in the menu.xml. Something like the following...
CODE |
Menu.xml
Game 1 ...
Game 2 ...
recent.xml
|
CODE |
Recent.xml
Recent 1 ...
Recent 2 ...
|
... which would end up with a menu in MXM looking like
Game 1
Game 2
Recent 1
Recent 2
----------------------------------------
flatspot,
I haven't really used mxm_entry.xml files myself, so I don't know much about them without looking it all up
Would this allow MXM to autodir that recent folder without actually copying the xbe and supporting files into said folder?
This post has been edited by Splice: Apr 17 2004, 02:44 AM