Bdm update #1333
Open
Bdm update #1333
+44
−21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…einitalisation of all bdm modes
- Currently only works with mass0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request checklist
Note: these are not necessarily requirements
Pull Request description
Clean initialisation of opl_io_module_t was not being performed for additional bdm modes, this may have no affect but best to do it anyway.
De-initialisation of all bdm modes was being skipped.. only reason I can see for that is we're trying to use per device data after the fact, so I've fixed that.
Make sure current mode is set to visible before rendering BdmIndex images, this should fix a little bug @rickgaiser encountered at startup with
mass3:randomly rendering the index.Fix auto loading bdm games from args after the changes to bdm structure. fixes #1327