Quote:
Originally Posted by Jefferson
I wouldn't say we had issues, but we definitely didn't use commands this year. They overcomplicated the small tasks and made the more complicated tasks very difficult. Especially where we needed more time resolution than whatever cycle the commands were on. The compile time for that many objects was hard to stomach also.
Our 2013 code is up here if you want to see how we implemented commands:
https://github.com/FRCTeam16/TMW2013
I guess we are using commands one place this year, dashboard buttons. We have two or three things we need to do infrequently enough that don't need to be accidentally pressed on the joystick. Commands make that very easy.
|
Interestingly, I felt similarly when I tried to use CPP for commands last year. Since switching to Java I found Command base was fairly simple and it meant a good chunk of our code was much cleaner than comparable other methods. I know it has allowed us to iterate our code far faster. I'll have to dig into this code and take a look at your new code at CMP this year.
Of course, my day job is primarily ruby/javascript code so that could explain why CPP felt less intuitive.