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.

Sign up for GitHub

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

Jump to bottom

Make shuffleboard not kill our performance #114

Open
danielbrownmsm opened this issue May 10, 2020 · 4 comments
Open

Make shuffleboard not kill our performance #114

danielbrownmsm opened this issue May 10, 2020 · 4 comments
Labels
low priority Low priority tasks

Comments

@danielbrownmsm
Copy link
Contributor

Make a toggle button on shuffleboard for being in “test” mode or “comp” mode. Comp mode would only update competition-necessary values. Test mode would update all. This should reduce the “0.02s loop overrun” or whatever warning we keep getting
@danielbrownmsm
Copy link
Contributor Author

Linking #a6d6cdbbdc51e441db33c2f353d1978100f77ef0

@danielbrownmsm
Copy link
Contributor Author

Linking feat/fastshuffleboard

@danielbrownmsm danielbrownmsm added the low priority Low priority tasks label Nov 2, 2020
@danielbrownmsm
Copy link
Contributor Author

To expand this, there should be different values (preset in Constants.java, updated with Shuffleboard). 0 would be comp-mode (bare-minimum stuff we need when competing). 1 would be a level up from that. 2 would be one up from that. 3 (or whatever) would be everything.

@danielbrownmsm
Copy link
Contributor Author

Could also make these levels modify not only them being read from, but also written to (i.e. whether or not the user modifying them is registered)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
low priority Low priority tasks
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@danielbrownmsm