View Single Post
  #4   Spotlight this post!  
Unread 17-01-2016, 12:54
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Deleting a subsystem

Makes sense. I think the wizard started to copy the files and didn't want to step on ones that had the same name. So delete them from disk first or give them a unique name.

By the way, the wizard refers them as operations because they will not likely be one-for-one with commands. One operation of Set arm height can be used for one command with a height parameter or numerous commands with constant heights such as -- Arm to floor, arm to max height, arm to draw bridge height.

So while it is a slippery slope, I found it useful to keep operation (a set point value) separate from command (a group of set points that includes an operation).

Greg McKaskle
Reply With Quote