Starlight220
Starlight220
Still need to think a bit more about how to do this.
This is mostly a change in documentation/recommended usage. The current (value) semantics of C++ command-based cause object slicing, which is difficult for both team and WPILib code. For decorators, there's...
This refers to specifically commands themselves, not the button bindings stuff (that's in #4218). All this is subject to change and happily up for discussion. - [x] #4245 - [x]...
Due to this being a relatively small change, I'm opening this issue for design discussion as opposed to a full design doc. I'm also bringing together the discussion of `interruptible`...
closes #4303 Once this is more advanced, check whether renaming `CommandPtr` to `Command` (removing the current `Command` class at the head of the inheritance hierarchy) would help reducing breaking changes...
This is all subject to change etc. Up for discussion. - [x] Initial API: #4104 - [x] Add examples - [x] wpilibsuite/frc-docs#1827 - [x] #1888 - at the `BooleanEvent` level...
`NetworkButton` should be pulled up to be a direct subclass of `NetworkEvent` (naming TBD); the alternative solution for its use-case--NT(4) listeners--isn't as much of a solution for the same problem-space...
> It's probably this: ```cpp enum AxisType { kXAxis, kYAxis, kZAxis, kTwistAxis, kThrottleAxis }; ``` _Originally posted by @calcmogul in https://github.com/wpilibsuite/allwpilib/pull/4230#issuecomment-1126987665_