QMamehook v1.9.3 - Blanco
The "Oh Parace, it's been THAT Long?" Update
Apologies for the time since releases. I've been very busy with OpenFIRE developments, plus some life happenings. I only managed to get enough free time starting this week to actually bundle everything up into a new release, because there's been a LOT of developments:
- Devices are now sorted based on device Product IDs, courtesy of @samuelballantyne
- Device strings (in
VID:PID @ portPath
format) are now printed whenever a specific port is referenced- Initial implementation courtesy of @samuelballantyne, with some added polish by myself
- Device info for whitelisted devices are printed at startup, courtesy of @samuelballantyne
- The current QMH version is now printed at startup
- QMH should now build fine with Qt5 or Qt6
- Initial implementation courtesy of @samuelballantyne, with some added "polish"(?) by myself
- If your system has more than one Qt version installed, you can force the specific version to be built against by adding
-DQMH_QT_VERSION=Qt#
to your initialcmake ..
command before building.
- QMH now has help text! This pops up when either inputting an incorrect custom path (
-p
) or calling for it with-h
/--help
.- This will also display QMH's default location where it searches for
.ini
s appropriate to the OS it's running on.
- This will also display QMH's default location where it searches for
- Custom paths
-p
are now checked to make sure they actually exist, and throw an error if it doesn't. - A lot of minor optimizations - or rather, pruning of some bad coding practices from past-me.
- When closing a connection (either voluntarily or because of a
mame_stop
command), QMH will now actually try and use the definedMameStop
field, if any.- If it doesn't find a MameStop field (or at least one that can be read as a list of commands), then it falls back to the old behavior of simply sending
E
to all devices before closing them. - QMH will also check after a configured stop script if there were any devices left over that haven't been closed yet, and force-close them as appropriate with a notification in the console log.
- If it doesn't find a MameStop field (or at least one that can be read as a list of commands), then it falls back to the old behavior of simply sending