Joystick enum Axis

[infrared511]

Is it possible to change the enumerator numbers in the Joystick.hpp Axis? I know you can edit and change it, but does that affect the rest of the Joystick implementation? My issue is the axis numbers and button numbers are often the same and causes conflict with my bindings when checking the joystick with a constant update, not the event. For instance, PovY = 7 while the right trigger(Dinput) also = 7. Both trigger it's the joystick, but then the ints are the same. With Events, this is kept separate as the events separate Axis and buttons. If I could change the Axis enumerator to start at 12 instead of 0 there will be no int clashes between buttons and Axis's while checking real time.

I hope this made sense and
Thanks.

[Nexus]

Each Axis is represented with a different enumerator, with a unique number:

    enum Axis
    {
        X,    ///< The X axis
        Y,    ///< The Y axis
        Z,    ///< The Z axis
        R,    ///< The R axis
        U,    ///< The U axis
        V,    ///< The V axis
        PovX, ///< The X axis of the point-of-view hat
        PovY  ///< The Y axis of the point-of-view hat
    };

Joystick buttons on the other hand are integers, indexed starting from 0. You can easily solve your problem by not mixing Axis and Button -- this is the reason why different types are used to represent both in SFML.

Of course, if you need to have a single address space to represent both axis and button (e.g. for serialization), it should be an easy exercise to achieve that in client code

By the way, in case you use Thor, I'm providing functions to serialize joystick axes from/to strings. This would allow you to display this in the game's UI. The documentation can be found here.

[infrared511]

Right, but button RT = 7 and so does Axis PovY, they are both integers. I understand keeping them separate, and they are as events. I guess I do not know how to accomplish real time updates while keeping them separate in my code. My original question still stands, will changing the Axis enumeration affect the rest of the code?  To ask further on your solution, how using a Switch Case can I separate real time axis and buttons?

[Laurent]

Real-time check of axis position is done with Joystick::getAxisPosition.
Real-time check of button state is done with Joystick::isButtonPressed.

There's no way you can have a conflict.

If you still have troubles, please give more details about (or show) the code you've written.

[infrared511]

Real-time check of axis position is done with Joystick::getAxisPosition.
Real-time check of button state is done with Joystick::isButtonPressed.

This is Specific. I can not see if ANY button/axis is registering a press, only a specific button/axis.

If I am updating to see if any button or axis is pressed, like sf::Event::JoystickButtonPressed, then there is a conflict as there is nothing in SFML to allow me to real time check this(Unless I am wrong). I can however check in real time if ANY axis/button is pressed by using the enum values, which as I said overlap. Simply starting axis enum at a higher number would fix this. I am not sure why nobody will answer my question asked so I will just do it and see.

  Thank you anyway.

[eXpl0it3r]

I think there's a fundamental misunderstand of either what you're trying to do (thus Laurent asked for some code, so we can understand), or your understanding of how SFML operates.

I can however check in real time if ANY axis/button is pressed by using the enum values, which as I said overlap.

That's the part we're not understanding here, as SFML doesn't provide such a functionality, how would you go about doing this?