View Single Post
  #1   Spotlight this post!  
Unread 20-08-2012, 15:29
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,112
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: Tips for first-year programmers

Quote:
Originally Posted by ctccromer View Post
Also, I forgot to mention: The last 2 years (our first 2), we've used Joysticks. However, being a huge gamer, I'm switching to the xbox360-like controller.
Are you doing this as a driver who prefers a handheld controller to joysticks for driving a robot, or are you doing it as a programmer who's imposing his preference on the drivers? Give proper consideration to the people who actually have to use what you come up with.

Quote:
So any tips on how this is different will help too!
Gamepad thumbsticks don't give a driver nearly the same amount of fine control that you can get from joysticks. If you can account for that in software, great. Otherwise, make sure the drivers are happy with what they get.

A gamepad puts more buttons within immediate reach of an operator's fingers than a joystick does. Some people find that useful. Others find it confusing, and prefer the more spread-out button layout of one of the USB joysticks from the Kit of Parts.

On the other hand, sometimes the most intuitive and effective control scheme is neither a joystick nor a gamepad, but instead a custom array of buttons and/or switches and/or knobs.