Skip to content
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

Sendable chooser values changes when robot starts #2

Closed
bradamiller opened this issue May 17, 2016 · 1 comment · Fixed by #6
Closed

Sendable chooser values changes when robot starts #2

bradamiller opened this issue May 17, 2016 · 1 comment · Fixed by #6

Comments

@bradamiller
Copy link
Contributor

Many teams experienced an issue with the SendableChooser widget in the SmartDashboard and robot code that caused the selected auto mode to not be the one that is run. The issue is that SmartDashboard would come up with the saved layout including the SendableChooser. The team would select the desired auto mode. Then the robot comes up, with the actual SendableChooser object that sets the selection to the default value. The team dashboard selection is then overwritten in NetworkTables.

A possible solution to this is to make the dashboard selections stick. That is when it notices the change from robot that is different than it's displayed UI, just set it back again. This makes sense to me since the sendable chooser UI element is supposed to represent the value returned when the robot grabs it.

@ThadHouse
Copy link
Member

Looking through this issue and wpilibsuite/allwpilib#206, this is actually caused by SmartDashboard not updating the selected value when a server is connected. The robot side code does not actually send a selected value, so the robot just ends up using the default value. We are planning on adding a connection listener to SmartDashboard where upon server connection the selected value will actually be sent.

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 a pull request may close this issue.

2 participants