1,079
edits
Difference between revisions of "Auto detection"
Jump to navigation
Jump to search
→Building blocks: Explain how 'detect' would be implemented
(Added some more thoughts on how to implement the revised detection code) |
(→Building blocks: Explain how 'detect' would be implemented) |
||
| Line 68: | Line 68: | ||
# If the size of <code>gameList</code> does not equal (i.e. no unique match was found), abort with an error | # If the size of <code>gameList</code> does not equal (i.e. no unique match was found), abort with an error | ||
# Finally, create a suitable Engine instance | # Finally, create a suitable Engine instance | ||
Note: I am not yet sure how to handle target_md5 here. Maybe we don't need it anymore, maybe it could be passed as a hint to <code> detectGames </code>. | Note: I am not yet sure how to handle target_md5 here. Maybe we don't need it anymore, maybe it could be passed as a hint to <code>detectGames</code>. | ||
The 'detect' part should be pretty obvious now: | |||
# Invoke <code>detectGames</code> to obtain <code>gameList</code> | |||
# Compute a new list from that, keeping only the gameid, platform, language values | |||
# Remove any duplicates from that new list (since we drop some information, some entries may suddently become identical) | |||
# Return this list to the caller | |||
=== File name handling (revising the SubstResFileNames system) === | === File name handling (revising the SubstResFileNames system) === | ||