Properly calling a Logitech Attack 3 Joystick Class

[Alan Anderson]

Originally Posted by Travis Hoffman

I don't enjoy diverging from the well-beaten path, so if there was a way to instantiate a standard joystick class to fit an Attack 3 without making a custom class, I'd be all for it, which is why I asked.

There does seem to be a way in the basic Joystick class to remap axes to the X/Y/Z/Throttle functions, but I don't use C++ enough to have tried it.

As for the custom class, it doesn't help matters much when the WPILib C++ source code location isn't a heavily advertised thing...I found it...but it doesn't seem to be something that is as readily available as it was in the past.

What do you need the source code for? All you'd be doing is inheriting from and extending an existing class. You wouldn't be reimplementing any of the lower-level code.

We read all joystick and gamepad values into more functionally-descriptive variables, and this code is well-commented to provide a cross reference between actual controller axis/button and function, so using "GetZ" or "GetRawAxis" won't be an issue.

Such cross-referencing would seem to be a natural fit for a brand-specific joystick class, and perhaps even a higher-level "driver controls" class as well. Maybe you're thinking of something more complicated than extending the base class, but I don't believe that much work is called for here.