iop parsing: make the PictureGraphic data size check less restricitve #531
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.
I came across an implement (Kverneland Andex1304) which contains a PictureGraphics with 0x0 actual size and 0 raw data size. Later in the pool it contains the same PictureGraphics object with correct dimensions, but the parser bailed out on the first zero size.
Fixes martonmiklos/AgIsoVirtualTerminal#2
How has this been tested?
Built AgIsoVt with this commit an the Kverneland Andex1304 loads fine.