Home Page Forums MAME QMC2 Questions, suggestions or requests topic

Also, there's a way in QMC2 to filter the listing to just some pre-selected categories?
For example, I'll use ASH MESS category and just only system with tags "Game console" and "Handheld Game Console" to be displayed.
If not possible now, here goes my suggestion

Fixed in SVN r5822 .

We've had that before... it will be possible in the "reg-exp filtered view" when that's available .

Oh, that's will be a very a nice feature when be released. I'll anxiously waiting for this feature release
And maybe I use more UME builds after that!

Another bug reporting.
There's a strange formating bug when using UME version of QMC2:


Left is Machine info tab for MESS QMC2 and Right one is the same Machine info tab, for the same sysinfo.dat file

The same problem happen when displaying the templates...

That's no bug but expected behavior because the UME variant uses the MAME history.dat formatting... only the MESS variant uses its own sysinfo.dat formatting. That's what UME brings us because there's no way to find out if a set is from MAME or MESS, that is, I decided for the formatting of the majority of sets (which are the ones from MAME, of course)... so get used to it or use the MAME/MESS variants separately, which is what I recommend to everyone.

I'm currently trying to change the respective code in order to keep an info where the data came from (history.dat / sysinfo.dat) and to act accordingly before displaying the data.

That's now supported in SVN r5825 .

Thank you, René

I think that I never asked, but why qmc2NEO queries it's necessary to be especified differently for MAME/UME and MESS? For example:
for MAME/UME

and
for MESS.

The best part is even when using a MESS driver in UME, "game" behaves as a MAME driver, don't being necessary for MESS its necessary to especify as "machine" nowdays. In other words, that's mean that a standarization may be possible


A little test of mine. I changed all "//machine" for "//game" and tested.

Well, I don't know if this is up your or MAME/MESS/UME scope, but if you can do this, such stadization are very welcome, because there's a lot of comparisions just for this thing (at less in my templates), and I'm sure that if it's been standardized, not only the template code can become simpler (and easy to maintain) as also will occupies less memory and require less processing for a fast scrolling between systems (yup, it will gain a perceptible speedup).