Re: FTC Functions Guide - Version 1
Unfortunately this feature was removed by FIRST and National Instruments. ROBOTC still supports it, but there's no way to toggle the variable in any version of the Field Management System or Controller Station. It's useless, so I left it out of the documentation.
Not a bad suggestion. I can update to explain which value is true and which value is false. I'm not sure an enum is required, however, since it is a Boolean value.
We'll leave this up to the user, but it's not a bad suggestion.
Our testing showed that using joy1Btn(btn) and joy2Btn(btn) was well understood by teams. I'd be up for changing it, but we'd have to leave the legacy version in place to avoid breaking teams already developed code. I agree with the inconsistency of the structure, but these are macro/functions and not variables.
To make programming easier for teams, all three software languages switched to a "two-program architecture". By keeping the auto/teleop code separate, you do lose the ability to transfer variables between the programs, but it makes programming much easier for new programmers. The old style template could still be used, but it seems like everyone is promoting the two-program style. I'll try and make something up to illustrate how this works.
Yes. I'll update this in version 2.
Agreed. This is more of a motors/sensor setup explanation though, which may be a separate guide. The PID capabilities have been simplified to a checkbox under the motors tab.
It's coming soon...
ROBOTC Developer - SW Engineertfriez@robotc.net