Fields and methods should not have conflicting names like DEADZONE. While this is technically legal it can lead to misunderstandings and problems with serialization.
Consider assigning this magic number 4 to a constant.
Using constants for hard-coded numbers is a best practice. A constant’s name can explain the rationale
behind this magic number. It is also easier to find if you ever need to change it.
Loading history...
35
public static double RIGHT_Y(Joystick joy) {return deadzone(joy.getRawAxis(5));}
Consider assigning this magic number 5 to a constant.
Using constants for hard-coded numbers is a best practice. A constant’s name can explain the rationale
behind this magic number. It is also easier to find if you ever need to change it.
Loading history...
36
public static double LT(Joystick joy) {return joy.getRawAxis(2);}
Consider assigning this magic number 2 to a constant.
Using constants for hard-coded numbers is a best practice. A constant’s name can explain the rationale
behind this magic number. It is also easier to find if you ever need to change it.
Loading history...
37
public static double RT(Joystick joy) {return joy.getRawAxis(3);}
Consider assigning this magic number 3 to a constant.
Using constants for hard-coded numbers is a best practice. A constant’s name can explain the rationale
behind this magic number. It is also easier to find if you ever need to change it.