Conversation
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
Note for future: - Drive do wierd things when CAN ID's overlap with mechanisms
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
GreenTomato5
left a comment
GreenTomato5
left a comment
There was a problem hiding this comment.
Lgtm, a few smallish things kind big idrk
| } | ||
|
|
||
| public ShooterStates getShooterState() { | ||
| // The WINDING_UP state's shooter target depends on the alliance at runtime. We |
There was a problem hiding this comment.
why? also if this is necessary cant the shooter state handle this? I feel like this shouldn't be a manager problem
There was a problem hiding this comment.
yes but would lead to annoying shooter states so i think its fine
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
|
✅ State machine graph generated and uploaded. |
2 participants
No description provided.