Fix issue with vision bounds not including the vision origin - #4645
Merged
cwisniew merged 1 commit intoJan 21, 2024
Merged
Conversation
The vision sweep is only well-behaved if it has bounds surrounding the origin. It is not enough that we use the vision bounds since certain cases may not guarantee that the vision shape include the vision origin. So we now make sure to explicitly expands the sweep bounds to include the origin. Also some separation of concerns: `EndpointSet` has no reason to know anything about vision, not even just to provide initial bounds. So now it only tracks the bounding box of its contents and nothing else.
cwisniew
approved these changes
Jan 21, 2024
kwvanderlinde
deleted the
bugfix/4637-vision-sweep-bounds-not-around-origin
branch
November 26, 2024 23:15
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Identify the Bug or Feature request
Fixes #4637
Description of the Change
The vision sweep is only well-behaved if it has bounds surrounding the origin. It is not enough that we use the vision bounds since certain cases may not guarantee that the vision shape include the vision origin. So we now make sure to explicitly expand the sweep bounds to include the origin.
Also some separation of concerns:
EndpointSethas no reason to know anything about vision, not even just to provide initial bounds. So now it only tracks the bounding box of its contents and nothing else.Possible Drawbacks
None
Documentation Notes
N/A
Release Notes
This change is