-
Notifications
You must be signed in to change notification settings - Fork 3
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
Tele op action #1
base: master
Are you sure you want to change the base?
Conversation
… StickyGamepad is now updated within the Robot
… selection of autos
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few things to consider:
You can't have multiple teleops with different button mappings if subsystems capture button input themselves.
Button mappings will also be spread out between multiple files, which may be desired, but also could make it easier to accidentally map one button to multiple actions.
import com.acmerobotics.robomatic.util.StickyGamepad; | ||
import com.qualcomm.robotcore.hardware.Gamepad; | ||
|
||
public interface TeleOpActionImpl { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Impl is short for Implementation, this is an interface
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you had some abstract interface and then a default implementation of that interface, you would call the implementation interfacenameImpl
I noticed the commit adding the field image, go ahead and merge if you want @jbeta02. |
No description provided.