You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The upcoming 9.0 release of the SDK will switch all usages of the term OpMode to the form "OpMode". FTC Docs does not consistently use the form "OpMode", and should be updated to do so.
Additionally, the preferred way to refer to OpModes that specifically extend LinearOpMode (including Blocks OpModes) is "linear OpMode", and the preferred way to refer to OpModes that specifically extend OpMode directly is "iterative OpMode".
The text was updated successfully, but these errors were encountered:
NoahAndrews
changed the title
Standardize on "OpMode" / "linear OpMode" / "iterative OpMode"
Standardize on "OpMode" / "linear OpMode" / "iterative OpMode" / "Blocks OpMode"
Aug 16, 2023
Doing that with case-sensitivity turned off is likely to catch the vast majority of instances, if not all. I'm not sure offhand if there are other places where the incorrect form is used.
The upcoming 9.0 release of the SDK will switch all usages of the term OpMode to the form "OpMode". FTC Docs does not consistently use the form "OpMode", and should be updated to do so.
Additionally, the preferred way to refer to OpModes that specifically extend
LinearOpMode
(including Blocks OpModes) is "linear OpMode", and the preferred way to refer to OpModes that specifically extendOpMode
directly is "iterative OpMode".The text was updated successfully, but these errors were encountered: