DrewNaylor
If we can't find even one manifest when extracting and moving or loading them, none of the following manifests will be extracted.
Solution: continue extracting manifests if the user tells us to. We have to change the current dialog box so it also has a warning icon. Possible message after what's already there:
Continue extracting manifests?
----------------------------------
[Yes] [No]
Maybe it would be a good idea to have this be "Continue processing manifests?" instead so it can also be used when loading manifests. There should also be options in the Options window to ignore this warning (three radio buttons: Always ask, Continue processing, and Stop processing), as well as a checkbox that says Don't ask me again, which means I need a custom messagebox and the warning icon probably can't be used unless there's a way to load it from a system icon namespace/class or something.
I'm going to tentatively mark this as "basically closed" since the only file I was having issues with was one that was too long. It'll also be removed from the readme for v0.3.0.2.
This is way later and I should've mentioned this earlier, but during testing I found out that the extraction code doesn't listen to the "no" choice and will ask repeatedly. This appears to be due to being async when extracting. There needs to be a way to have it activate a cancelation token or something to force it to stop.
Edit: I did mention this in #153, apparently.
May as well close this, because it was only an issue with manifest paths that were too long.