External integrations already have access to the CURRENTPATH,
FULLPATH and STARTPATH files in order to see which file is currently
active in the file selector and which core was started.
Unforuntately there is no way for the integration to see when
the file selector closes and whether the file was selected or
the selector was cancelled. In my use-case, I have an external
display showing game data and marquee images. When the file
selector is active, this display shows data about the current
file selection. When a game is running it shows info about that
game. Without a way to know if the selection menu is visible, the
transition from displaying the highlighted selection to displaying
the active game is impossible when the file selector has just been
cancelled. I also want to be able to use the extra data about the
game that has been picked within the console menu. That data is
available in CURRENTPATH, but if the menu is cancelled, we don't
know if it's valid to use or not.
This new file just tracks the status of the file select menu.
When the file selector menu is onscreen it contains "active".
When cancelled it contains "cancelled".
If the file was actually chosen it contains "selected".
That set of extra information is enough to know which game
is currently running and which is just under selection regardless
of whether the menu was cancelled or actually selected.
Note: there are almost certainly nicer ways to expose all this
information, but I'm attempting to keep any existing integrations
that use these files working without requiring any changes.
`preset_default` option added to ini. Filename is relative to the presets/ path.
"Reset to defaults" option added to video processing menu which will delete the config files and reload the default configuration.
For a while the Minimig core has only made it possible to select ROM files in the Amiga folder directly. But many Minimig users have quite the collection of different Amiga ROMs though, so being able to have several sub-folders with kick ROMs for the core really helps.
Previous implementation only catchs gamepad buttons BTN_GAMEPAD.
This commit add support for joystick button BTN_JOYSTICK.
Useful for lightgun devices using HID report type Joystick.
The current strings for `joy_button_map` are not as intuitive to the user as they probably could be. This proposed change will help the user know what is meant by the defining the axis of the joystick by referring to the stick the same way as it was referred to during the earlier controller test step. If there is a better way to do this or this is not appropriate, that's okay too. :)
