Add osd_lock and osd_lock_time config options
When osd_lock is set it specifies a sequence of button pressed that must be pressed in order to gain access to the OSD while running a core.
osd_lock_time is the time (in seconds) before you will be prompted again for the unlock code after you have closes the OSD.
Co-authored-by: Martin Donlon <github-martin@donlons.com>
- Send audio sectors faster so buffer stays filled
- Ask FPGA if it is ready to receive a sector
- Fix SCAN with CHD files
- Fix missing start of audio by sending with separate index
Add ini option `unique_mapping` which makes controller mappings unique to the physical port the controller is connected to.
Calculates a uint32_t unique_hash for each device during enumeration.
Co-authored-by: Martin Donlon <github-martin@donlons.com>
Treat SendDataRequest sane as SendStatus during Latency wat periods. It was freezing only when "Normal Seek" was in place; this seems to be a result of sending data requests during wait periods, when statuses were not sent.
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.
