Quote:
Originally Posted by Ginto8
<snip> There may be an issue with the internal Command killing the CommandGroup it is called from because they each require() the same Subsystem. I will see what I can do to mitigate that.
|
Yeah, that's exactly the issue we ran into last year. Another drawback we found is that if you put a button on the SmartDashboard for this kind of nested command, you can't click on the button again to cancel the command like usual, because the original command already finished execution, it's the newly instantiated command that's making the robot move.
Anyway, I'll be interested to see what solution you come up with!