Main > Software Forum
Has someone mcm.ini and mame.xml (and controls.dat) combined?
(1/3) > >>
MaMeNnO:
I want to display info about games in my front-end. I want to display 'manufacturer', 'year', 'catagory', 'sub catagory', 'button X info', 'additional info about game' and be able to filter on some.

This information seems not to be available in one file. I did a search here as well with mr. Google to find out if someone ever did combine the info from MCM.INI and MAME.XML and CONTROLS.DAT, but to no succes. Actually I can't really imagine that this has not been done yet. :dunno

Maybe there is someone that has done this allready? ;D

If not, well, I have to do it myself. To be honest, I have done some stuff myself allready (because of the above).
Howard_Casto:
I mean no offense, but it hasn't been done because it's a dumb idea. 

Adding all of that info to a single file would result in a HUGE file.  What we (and by we I mean fe developers and emu app developers) do is read all the files seperately and combine data on the fly when it's displayed.  Most front-ends already do this.  Dk, for example, can display all of that, save controls.dat and filter it out exactly like your are saying.  The only reason controls.dat isn't supported is the last public release pre-dates the dat and it'll be added later. 

A note on MCM though... it's a rather useless file imho, with the exception of a quick file sort.  What you do is get a copy of catver.ini and filter off all games with the *mature* flag tacked on.  It's more work, but you get the same results and have the added benefit of filtering by regular genres as well. 
MaMeNnO:
that figures! ::)

Well thanks anyway for the insight. Then I'll just read 'em seperately and join the whole bunch in memory.
NOP:
I can actually see this as being a useful thing (at least controls and mame's xml).

For my own pet project, ROMLister, controls.dat has some really useful information, but it lacks the screen orientation data that I also use.  Currently, ROMLister opens either of the 2 files, and you get to work with whatever data is inside each.  Having them combined into 1 file would (for me) be the best of both worlds.

I almost starting writing a program that does exactly what you're proposing.
If you write one, I'd use it.  If you write it in C++ and open source it, I'd fold your code into my project and give you a big kudos.

For my purposes, if you took mame's xml output and skipped all of the ROM CRC details, and merged it with controls.dat, you'd actually end up with a smaller file to work with.  My software isn't written in a way that loading in both files and merging would be useful-I never actually read the entire file in at once at any time.

http://www.waste.org/~winkles/ROMLister

-jeff!

MaMeNnO:
I my FE I have a dedicated XML parser that reads the whole mame.xml file (line by line) and just grap the name, cloneof, description, year and controls (type) info. I also read the whole catver.ini file. I'm about to write the part that joins the whole lot. I wrote it in VB6.0 Not really pretty code, but that's because I didn't know VB and learned it as the project progresses.
I guess you can read the VB code and translate it into C++.

I'll PM you when I'm ready!
Navigation
Message Index
Next page

Go to full version