|
> Use Logiqx "supplement" datfiles instead.
I thought "supplement" datfiles where used to scan for files that are used by emulators that had common roms with Mame. This is sort of opposite of what I am trying to do. What I would like to be able to do is have a folder strucuture something like ./mame/roms/raine ./mame/roms/cps1 etc. Then you take a dat file from your other source (ie Raine) and split it into two parts - supplemental and mame'd. You could then treat the mame'd dat file like a bios based system. the way I used to accomplish this (when I actually had the time to do it) was get a complete mame set built first, then start "rebuilding" the subsystems from the complete mame set into their destinations so they would be in the correct directories. Maybe it is just me being a real pain asking for something that is not easy to implement and that no other other than me would use but it seemed like what I was doing was nearly identical to the scan being run for the "systems" portion of a Mame scan.
Maybe I am being delusional but I thought with the "systems" feature you could define a default path for that system and the scanner would let you know when something from that system was outside of its default path. While the current system can only define one path it would be nice if you could define a "primary" system path where the bios file should reside and multiple "secondary" paths so that large systems, such as NeoGeo, can be spread across several folders.
Speaking of paths, that is another thing I would like to see changed in ClrMamePro. For my Mame collection I have about fifteen directories I keep roms in and from time to time I change their names. In order to put the paths back in I have to manually re-add them. It would be nice if you could open up the existing paths in some sort of text editor (even a text box in the application) and edit them.
Thanks again for your excellent program.
ac.
|