#Robotc programming guide vex how to#

Really, you are doing YOURSELF a huge favor by putting comments in your code.

And god forbid thereвЂ™s a programming emergency at a competition, and none of the teamвЂ™s programmers are there (or you, if youвЂ™re the only programmer) now people who are not experts at programming are going to have to start poking around in your code, changing stuff, and praying.

Without comments, the next programmer will waste lots of time (a) figuring out what you did, or (b) assuming your code does X when it really does Y, and adding more code, assuming the stuff thatвЂ™s there does X.

When your team has multiple programmers jumping in and out of the code, comments are vital so that other programmers can understand what you have done and why youвЂ™ve done it. When you write some code, and the robot doesnвЂ™t do what youвЂ™re expecting, having comments placed throughout your program will help you evaluate the code youвЂ™ve written - does the code below do what the comment says it should do? ThereвЂ™s really no excuse for not putting comments in your code, whether youвЂ™re using easењњ or RobotC, or any other language on this earth. Adding a floor/ceiling to your calculated motor power.In this post, I go through the following: In RobotC you must program these items yourself. Unlike easењњ, the standard text-based RobotC does not have joystick blocks that one can simply drag and drop and poof! you have arcade drive.

#Robotc programming guide vex how to#

This week, I learned how to program a joystick to drive a chassis.

I will post things here as I learn them, that might be helpful to others who are also new to this language. This post is part of my journey from easењњ to RobotC.