fix reading XRECORD objects with no duplicate-handling flag #62
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.
When reading and
XRECORD
object, the only possibilities following the100/AcDbXrecord
code pair are either a code280
which indicates the duplicate record handling flag, or a code102
which is just regular data.This moves the code
280
handler higher in the loop to account for the case where a code102
immediately follows the100/AcDbXrecord
pair which means any subsequent code280
must belong to the data section and not the duplicate record handling flag.Fixes #61
FYI @AleksandarDev