View Single Post
  #1   Spotlight this post!  
Unread 27-01-2017, 12:11
dmelcer9 dmelcer9 is offline
Registered User
AKA: Daniel
FRC #0810 (Mechanical Bulls)
Team Role: Leadership
 
Join Date: Dec 2015
Rookie Year: 2012
Location: Smithtown
Posts: 51
dmelcer9 is an unknown quantity at this point
Re: Building Commands at Runtime

Quote:
Originally Posted by wlogeais View Post
So what exactly is the problem with this required-whole-time status, and how does supplier/optional change that at all? (since you are still added same subsystem-commands into a group)
Oh, I'm saying that doing the supplier/optional/commandgroup setup allows the required whole time, while instead doing a custom implementation of commandgroup doesn't allow that. The required whole time feature is good because any subsystems that need to be in a certain state for the command group to function optimally will be in that state the whole time the command group is running.

Quote:
Originally Posted by wlogeais View Post
I just prefer the simplicity of a single chooser, eg. FuelThenGear as an option and the ability to not add GearThenFuel if it isn't going to be tested and used.
That's just driver preference I guess- our drivers liked the "building" the autonomous sequence before each match. Sometimes the alliance partners have weird robots or strategies, so it's good to have a modular system for any scenario.
Reply With Quote