QMC2 v0.2.b20 is released. M.A.M.E. Catalog / Launcher II (also referred to as QMC2) is the successor of one of the first XMAME GUI frontends available, QMamecat (derived from MAMECAT, which was text-only). QMC2 has been rebuilt from scratch as a Qt 4 project. Parts of the design and code were inspired by its predecessor. The new design was made as flexible as possible to minimize dependencies from frontend- and CLI-related MAME changes, which was a major deficiency of QMamecat. QMC2 uses a template-based MAME configuration scheme, which can easily be enhanced with additional command line options (defined in an XML template file).

QMC2 v0.2.b20 Changelog:
- fix: ROMAlyzer / checksum wizard: correctly handle ROM files when their names contain special characters (i.e. ´&´)
- fix: corrected the handling of repeated log messages (the repetition counter was correctly logged, but the actual new message was eaten)
- fix: remove Phonon effects asynchronously (aka QObject::deleteLater()) -- note that this finally also fixes the long-standing post-mortem crash on Mac OS X
- fix: file and directory edit widgets did only commit any data changes when they were ´edited´, but not when their data changed ´spontaneously´ -- see bug tracker ID #17
- fix: MESS targets: avoid crash when exiting while a device setup is open
- fix: emulator configuration: correctly position the text cursor for ´int´ and ´float´ option types as well
- fix: corrected hiding of category-/version-columns in the category-/version-views
- fix: embedder: under certain window-managers (i.e. KDE4 >= 4.6) the snapshot-viewer wasn´t correctly updated -- fixed by adding an explicit paintEvent() method which just repaints the background brush
- fix: Win32: emulator control panel: hide LED0-, LED1- and status-columns, because notifiers aren´t supported on Windows (yet)
- imp: SDLMAME/MAME/MAMEUIFX32 templates updated to 0.142u3 (new option menu for MAME, removed option uimodekey for MAME)
- imp: SDLMESS/MESS templates updated to 0.142u3
- imp: ghost image enhanced, including a derived ´no video´ pendant
- imp: improved log output when the validation of the emulator executable fails
- imp: MESS targets: added new / alternate emulator type identification string (´M.E.S.S.´ vs. ´MESS´) as used since 0.142 SVN -- see bug tracker ID #16
- imp: MESS targets: the device configurator now also saves / restores the last selected setup (if any) and includes a context menu for the device instance map
- imp: added an option to let the user decide if the ROM status icons are to be shown or not (see in game/machine-list tab of the main setup dialog)
- imp: avoid potential blocking when synchronously calling external programs
- imp: updated template format to v0.2.4 which adds support for a new ´combo´ option-type (editable combo-box with pre-defined choices the user can select from) and a new ´visible´ attribute to hide certain options (esp. to hide the ramsize option for MAME, where it´s not used, but the emulator still reports it as a valid option)
- imp: setup dialog: added the ability to reset a customized application- or log-font as well as to reset the style-sheet (note that the system´s default font will be gathered during startup, so if its value changes at run-time you will have to restart QMC2 for correct behavior)
- new: added command line option -qmc2_config_path to allow for overwriting the path where QMC2 stores its setup, caches etc. -- it´s in the user´s responsibility to copy/move the data to the desired directory (otherwise QMC2 will start over, which may be wanted behavior, though)
- new: support for game/machine attached YouTube videos (Phonon-based video player)
- new: added three tool-functions to allow for forced removal of any game/machine-list related cache data stored on disk
- new: added support to provide lists of available BIOS sets (MAME & MESS) and RAM size options (MESS-only) in the game/machine-specific emulator configuration widgets
- wip: completing the support for software lists -- basically working, but some planned functionality is still missing, and there are open questions regarding the official way to scan the hash XML data
- doc: added Q2.14, Q2.15, Q2.16 and Q2.17 to the FAQ

Download: QMC2 v0.2.b20
Source: Here