You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
There are some desirable features we could have during TeleOp. We would like to
x
is arm up andy
is arm down, we can combine these into aButtonPair(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.
The text was updated successfully, but these errors were encountered: