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
This one is a little bit tricky, since the controller is passed into the superclass constructor without assigning it. The super call must be the first statement in the constructor, so assigning it in the constructor before calling super is out. Making it a private field might be possible, but it can't be an instance object since instance objects don't get instantiated until after the constructor is run. It might be possible to make it a class object with static.
Another approach would be to create it in RobotContainer and pass it in as a constructor parameter. This follows the same signature as the superclass, so it seems logical.
Another approach would be to see if it is possible to retrieve the controller from the subsystem after it is constructed.
The text was updated successfully, but these errors were encountered:
Of course, we would also want the ArmPidSubsystem on the Shuffleboard. Perhaps a class that is an extension of the class ProfiledPIDSubsystem will automatically put the controller on the Shuffleboard if the subsystem is placed there?
The PID was put on the shuffleboard yesterday so that part is completed. However, it was asked to be displayed as % to be more user-friendly, so that is the next step to be completed.
All sendables should be on the Shuffleboard.
This one is a little bit tricky, since the controller is passed into the superclass constructor without assigning it. The super call must be the first statement in the constructor, so assigning it in the constructor before calling super is out. Making it a private field might be possible, but it can't be an instance object since instance objects don't get instantiated until after the constructor is run. It might be possible to make it a class object with static.
Another approach would be to create it in RobotContainer and pass it in as a constructor parameter. This follows the same signature as the superclass, so it seems logical.
Another approach would be to see if it is possible to retrieve the controller from the subsystem after it is constructed.
The text was updated successfully, but these errors were encountered: