Quote:
Originally Posted by GeoffR
Maybe an all-or-nothing option would be useful
|
It already treats each individual patch file as all-or-nothing; so if one patch depends on another patch, they should be in the same file; whereas independent patches can be split into separate files.
Quote:
Originally Posted by GeoffR
The idea should be workable for some patches that only modify data, but not for many of the ones that modify code, as often the code changes depending on its position relative to other code or data.
|
Of course, in an all-or-nothing mode, the idea of making at least some of the patches version-independent, is kind of useless. A single address patch (or single change to a patched string) would then block all others.
I'll put your updated patch32lsb in the next beta, I'll also try to get the USB hook in place for that one.