Skip to content
This repository was archived by the owner on Sep 6, 2024. It is now read-only.

Commit

Permalink
update readme
Browse files Browse the repository at this point in the history
Former-commit-id: c81bb27b6eafe999af0a24546df4163068d2f5bb
Former-commit-id: eb9c81f
  • Loading branch information
rgatkinson committed Sep 17, 2015
1 parent ff05a3c commit b27bcb9
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,16 +33,16 @@ Notable features of the Swerve Robotics FTC Library include:
components. The class builds on the latter to provide linear velocity and position indications
using integration in software.

The fifteen second summary of how to use the library is as follows:
The fifteen second summary of how to use SynchronousOpMode is as follows:

* Inherit your OpMode from SynchronousOpMode instead of OpMode.
* Inherit your opmode from SynchronousOpMode instead of OpMode or LinearOpMode.
* Implement your code in a main() method whose signature is:

@Override protected void main() throws InterruptedException
* Initialize your hardware variables at the top of main() instead of in start(). Otherwise,
the use of hardware objects (DcMotor, Servo, GamePads, etc) is the same as in the RCL, with
the single exception that the GamePad objects have methods rather than data, so you have to
say, e.g.,
the use of hardware objects (DcMotor, Servo, GamePads, etc) is the same as in the usual robot
controller runtime, with the single exception that the GamePad objects have methods rather than
data, so you have to say, e.g.,
```
gamepad1.left_stick_y()
```
Expand Down

0 comments on commit b27bcb9

Please sign in to comment.