ChdFileReader: Correct extension check #12076
Merged
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
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.
Description of Changes
This check would fail if the returned extension was
.chdAdditionally,
GetExtensionwould return the extension without., so no file would failRationale behind Changes
This issue only impacts chd files with parent chd files
When searching for the parent chd, we would trying to examine every file as a chd, instead of only examining chd files
Suggested Testing Steps
Test CHD files with parent CHD files and see if they still open
Such files can be created with
chdman createdvd -i "disc.iso" -op "parent.chd" -o "disc.chd"I'll note that chdman 0.271 and 0.272 currently has issues creating such files for PS2 sized games, so use an older version.