Quote:
Originally Posted by trycatch
it seems VERY overly complex, especially for brand new programmers, to require entirely separate classes for every single thing you want the robot to do, especially when every command class is a single function.
|
I've recently joined an FRC team as the programming mentor and went through a similar exercise.
The big appeal of command based approach for me is that it is its support for testing. By placing each robot function/feature into a command class then it's possible to wire up a Smart Dashboard button to each command and allow that single function/feature to be executed and tested separately.
I ended up having more problems trying to customise Smart Dashboard buttons than writing a command based robot example but that's a different story. In the end I got it sorted out and being able to test each command by pressing a button seems like a much better approach compared to large blocks of code in a loop.