Xbox Controller class

[GeeTwo]

Originally Posted by notmattlythgoe

Just a small nitpick from first glance, but is there a reason you didn't extend the Joystick class? This would allow you to use this class in any place a Joystick is used. We're currently working on one that overrides all of the joystick methods to map them to the buttons and sticks correctly.

Actually, this makes sense to me. The x box controller has a joystick.

[notmattlythgoe]

Originally Posted by GeeTwo

Actually, this makes sense to me. The x box controller has a joystick.

In the loosest term of joystick. The OP's reasoning for not extending the Joystick class is a more valid reason not to.

[Rakusan2]

As I been looking, extending Joystick class might make the choices of methods which I want to keep as few as possible too crowded for the programmer that is using my class.

[notmattlythgoe]

Originally Posted by Rakusan2

As I been looking, extending Joystick class might make the choices of methods which I want to keep as few as possible too crowded for the programmer that is using my class.

It definitely adds a bunch of new methods to the class, which can both be a good and bad thing. And there is nothing wrong with a simple class that sets all of the mappings to meaningful method names that aren't getRawAxis(2).

Overall, looks good. Well done.