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
Eventually, when a subsystem is being enabled for the first time, it needs to have its init() method called. This never happens so it will throw SubsystemUninitializedExceptions everywhere
The text was updated successfully, but these errors were encountered:
For the most part, this has been tested to work
# build.gradle
- Starting to try to simulate within WPILib
# frc.robot.Robot
- General maintenence
- SubsystemManager is now actually implemented and enables/disables subsystems
- Created a new method to send the normal status (which happens a lot)
- Manipulator control
- Switches what is active based on the direction of control (See Controls.md)
# org.longmetal.Arduino
- Documentation
- New PROBLEM Status. Needs to be added to UsefulRSL.ino (in master)
# org.longmetal.Constants
- Documentation for unclear values
- Values required for new things (manipulator stuff)
# org.longmetal.Shooter
- Can now do what it's supposed to
- Modifiers can be applied regardless of shooting speed
- Angle will work now
# org.longmetal.SubsystemManager
- SendableChooser s actually work now (as long as you call the `checkSendables()` method occasionally)
- Subsystems enable/disable cleanly (except for #17 )
# org.longmetal.util.Math
- Documentation
If a subsystem was not initialized, the first time we try to use it, it will throw a SubsystemUninitializedException and we can catch that and initialize the subsystem
Eventually, when a subsystem is being enabled for the first time, it needs to have its
init()
method called. This never happens so it will throwSubsystemUninitializedException
s everywhereThe text was updated successfully, but these errors were encountered: