Starlight220
Starlight220
The PR that closed this fixed the confusion, but doesn't deal with names for specialized colors.
I was thinking of adding a `string` constructor parameter that defaults to the RGB hex. That way it's cached for all objects, and not expensive at all.
Sounds like a good idea.
Any update on this? If the problem isn't on the RobotPy side, do we know more specifically where the problem is on the WPILib side?
`test`s would run on `deploy` if `deploy` depended on `build`. Since it doesn't, then tests would never run on deploy.
Since many teams rarely simply `build` but usually only deploy, the tests will almost never be run if they don't run on deploy. On the other hand, running tests could...
Expansion of #3442: > Setting a "safe/idle state" to subsystems is important, similar to `MotorController.stopMotor()`. This is especially important with control loops, it's easy to forget to `setpoint = 0`...
This doesn't have any user-facing changes, right?
If the `isReal` naming is confusing with Romi etc, how about renaming it to `isRoboRIO`? --- I think it's much more convenient and clear to directly check what is wanted...
I'll address these in the order of the table you posted: - Whether the code is deployed or ran on the compiling machine is easy to know at compile-time, and...