-
Notifications
You must be signed in to change notification settings - Fork 6
New robot controls #31
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
New robot controls #31
Conversation
enum class VisionModes { BALL, HIGHGOAL } | ||
|
||
class VisionToggleSubsystem() : SubsystemBase() { | ||
var visionMode = VisionModes.BALL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure it makes sense to make the vision mode (ball/high goal) a toggle. The driver has to remember which mode the robot is in, may have to switch frequently, and could get bad results if they choose the wrong mode.
It probably makes more sense to just assign high goal vision and ball vision to separate buttons. You could move climbing to the D-Pad, use the triggers for vision (ie - right high goal, left ball), and keep shooting on the right bumper (or something like that)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. I've sent you my thoughts on discord and may update the controls again before Thursday
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. See the comment about vision mode toggling -- you don't have to change it, but I would encourage you to.
No description provided.