thornworks
commented
10 years ago Nice! It's great when the time you put into learning a framework pays off in readability and flexibility.
One thing I meant to ask you about with that whole Drive-to-click concept... I thought only one command can use a sub-system at a time. So if the drive train is being used by the shooting system, does that mean the operator can't drive? And if the operator is moving, can we still wind? I expect that there shouldn't be a problem getting the machine to wind while you are driving but I thought the framework might stop you if both commands use the drive-train subsystem.
If it does take a little while to wind, then being able to set a winding value while moving around would be a nice feature.
On Thu, Feb 27, 2014 at 8:24 PM, Harshil Garg notifications@github.comwrote:
Closed #6 https://github.com/bethpage-robotics/Aerial-Assist/issues/6.
Reply to this email directly or view it on GitHubhttps://github.com/bethpage-robotics/Aerial-Assist/issues/6 .
-L. LaSpina proctinator.com
One of the really neat things about command-based coding is the relative ease of code modification due to the highly object-oriented and "multi-threaded" control. Don't like the driveToExactClick method if we can't test it? No problem. I would have to delete one line of code from the command group, highlighted here. I will close this issue upon further discussion, or response to your comments.