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

Finish the input mapping #7

Open
jamestmartin opened this issue Feb 8, 2018 · 0 comments
Open

Finish the input mapping #7

jamestmartin opened this issue Feb 8, 2018 · 0 comments

Comments

@jamestmartin
Copy link

There are some desirable features we could have during TeleOp. We would like to

  • Take references to input variables rather than copying their values
  • Rename buttons based on what they do rather than their position on the gamepad
  • Associate behaviors with buttons (event listening) rather than scattering input reading throughout the codebase
  • Produce buttons with combined behaviors and treating them as a unit (e.g. if x is arm up and y is arm down, we can combine these into a ButtonPair(x, y) and assign the arm behavior as a produced direction sign. This sounds complicated, but a demonstration would show that it isn't.

Since most behavior in TeleOp is based on input, I suspect this will drastically improve the codebase.

@jamestmartin jamestmartin self-assigned this Feb 8, 2018
@jamestmartin jamestmartin added this to Planned in Off season via automation Feb 8, 2018
@jamestmartin jamestmartin moved this from Planned to In progress in Off season Feb 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Off season
  
In progress
Development

No branches or pull requests

1 participant