Ignore virtual gaps in line objects #2266
Draft
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.
Line objects in .ocd files can contain virtual gaps, i.e., gaps that interrupt the line but keep the object as a single object.
Mapper does not yet support virtual gaps and thus ignores them when importing .ocd files.
Issue a warning that virtual gaps in line objects are not supported.
The current PR is a WIP as it depends on merging #2224.
If there a multiple objects with virtual gaps, only one warning should be issued. This is being accomplished by the first commit (which is a modified version of the one in #2124).