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

We should have a Button Mapping file #27

Open
Dylan-Powers opened this issue Apr 24, 2022 · 0 comments
Open

We should have a Button Mapping file #27

Dylan-Powers opened this issue Apr 24, 2022 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@Dylan-Powers
Copy link
Member

Dylan-Powers commented Apr 24, 2022

We should use a file unique to each robot to denote the controls. This file would be very similar to a Constants.h file in that it would use #define to define a literal for each button. For example #define INTAKE_FORWARD_BUTTON pros::E_CONTROLLER_DIGITAL_Y would define INTAKE_FORWARD_BUTTON to be the Y button. We could then pass it into the proper node as a button. This would allow us to very easily change controls without having to hunt them down in the rest of the project.

@Dylan-Powers Dylan-Powers added enhancement New feature or request good first issue Good for newcomers labels Apr 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant