resource_dasm now supports ID ranges. This probably changed the interactions between resource_dasm's various include/exclude options a bit. Honestly, I think they have become too complicated and should be simplified in some way.
IDs/ID ranges can be excluded instead of included by prefixing them with ~ (! can't be used because it clashes with the shell's history expansion).
ResourceIDs's constructor takes an enum instead of a bool to get rid of unwanted implicit conversions (e.g. from pointers) to bool.
resource_dasm now supports ID ranges. This probably changed the interactions between resource_dasm's various include/exclude options a bit. Honestly, I think they have become too complicated and should be simplified in some way.
IDs/ID ranges can be excluded instead of included by prefixing them with
~(!can't be used because it clashes with the shell's history expansion).ResourceIDs's constructor takes an
enuminstead of aboolto get rid of unwanted implicit conversions (e.g. from pointers) tobool.