-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Display outline of robot #47
Comments
@andrewda Awesome! Feel free to let me know if there are other issues you'd like to work on after this! |
Maybe support any polygon instead of just rectangle with length / width. Some robots have slightly more complicated shapes and it also allows people to personalize a little bit. Just take in list of points center of robot is 0,0 the points connect to neighbors etc. |
I'm surprised this ticket hasn't gotten more traction in the 4 years since it was opened. I'm working on a solution (https://github.com/SprinterDave/PathWeaver) which I'll hopefully get up for PR at the end of the season. The solution allows users to specify the rectangular bounding box dimensions of their robot and an optional top-down image of the robot. Non-rectangular robots can simply provide a transparent, top-down image of the robot (ex. cad drawing) that will then show the EXACT robot extents within the bounding box. |
Is your feature request related to a problem? Please describe.
Without a way to see the size of the robot on the screen, it is harder to determine where to start a path from and harder to check if if the robot will collide with a field element while following the path.
Describe the solution you'd like
The robot's frame perimeter appears at each waypoint. Data to create an outline of the robot could be pulled from an implementation of #26.
Describe alternatives you've considered
Alternatively, the robot frame could only be displayed at the start and end of each Path (Like Cheesy Path), or the UI could prohibit waypoints to be placed in areas that could cause the robot's frame perimeter to intersect with a field element.
Additional context
Screenshot of Cheesy Path
The text was updated successfully, but these errors were encountered: