Skip to content

Conversation

henrymwestfall
Copy link
Member

No description provided.

enum class VisionModes { BALL, HIGHGOAL }

class VisionToggleSubsystem() : SubsystemBase() {
var visionMode = VisionModes.BALL
Copy link
Member

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)

Copy link
Member Author

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

Copy link
Member

@edwardwawrzynek edwardwawrzynek left a 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.

@henrymwestfall henrymwestfall merged commit 54af5be into fairviewrobotics:master Aug 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants