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
Currently when the RobotGamePieceState == NoGamePiece, and the bottom, middle or top button is pressed, the arm will go the pickup location.
I'm starting to think this is a bad idea. Whenever the X button is pressed, it will go to the pickup location as long as we are not holding any gamepiece and it will rumble once it get's to the pickup location.
None of this functionality happens if you go to the pickup location using one of the other buttons.
Also, if you click X, then click A, then click X, each press will be a new ArmCommand which will try to go back the first waypoint.
If you just click X over and over again, it will only try to go the first waypoint once.
So I think the ArmSelectorCommand should do nothing if RobotGamePieceState == NoGamePiece instead of going to the pickup location. m_ArmCommand should be set to an InstantCommand to avoid problems.
The text was updated successfully, but these errors were encountered:
ErikCald
changed the title
RobotGamePieceState is no gamepiece but bottom, middle or top is pressed
When RobotGamePieceState is NoGamePiece but bottom, middle or top button is pressed
Mar 22, 2023
Currently when the RobotGamePieceState == NoGamePiece, and the bottom, middle or top button is pressed, the arm will go the pickup location.
I'm starting to think this is a bad idea. Whenever the X button is pressed, it will go to the pickup location as long as we are not holding any gamepiece and it will rumble once it get's to the pickup location.
None of this functionality happens if you go to the pickup location using one of the other buttons.
Also, if you click X, then click A, then click X, each press will be a new ArmCommand which will try to go back the first waypoint.
If you just click X over and over again, it will only try to go the first waypoint once.
So I think the ArmSelectorCommand should do nothing if RobotGamePieceState == NoGamePiece instead of going to the pickup location. m_ArmCommand should be set to an InstantCommand to avoid problems.
The text was updated successfully, but these errors were encountered: