> > Allow me to take this opportunity to demand of other MAMEdevs what I've demanded > for > > months now: Why in the hell do we not show the same missing-file info in the > internal > > UI as what we show on the command line? It's stupid. Just completely stupid. MAMEUI > > isn't great, but when baseline MAME can't even tell users in its own internal UI > > what's missing, yeah, I can't even blame people for going with MAMEUI. > > Because, as I'm sure you know, working with the code in question is far from simple. > But anyway, changes happen.
is there any chance the message could be a little more dynamic
one thing I've noticed over the years is that when pepole see 'or CHD' they instantly assume a CHD is missing, even for things that don't use them.
Maybe splitting the message into sections 'Missing ROMs' 'Missing CHDs' 'Missing BIOS' 'Missing device ROMs' and saying where each should be would help, as the added complexity introduced over the last few years is really throwing a lot of people off, they don't realise they need more than just 'the rom' If there's nothing missing for a certain category, don't show it.
|