Unclear intent of mappings about sdl_gamecontrollerdb HOT 4 CLOSED

This database is meant as a quick way to share mappings with others, easy to edit and update. SDL's internal mappings require a new binary to be updated, which can be a fairly involved process on some systems, and also Sam requires that the mappings shipped with SDL are "verified" (whatever that means).

from sdl_gamecontrollerdb.

Given my fiancée and I have managed to land patches in SDL itself for some controller mappings, it doesn’t seem that high a bar! 😜 I can understand if this is where more obscure controller mappings go, though.

Is the intent that equivalents to mappings included in SDL itself be added here as well for backwards compatibility? What’s the intent if backwards compatibility isn’t possible for a given mapping?

from sdl_gamecontrollerdb.

Proper support for the Xbox controllers in all platforms is important, that's why the patches got accepted quickly :) In the particular case of your changes, since you added functionality to OSX HID code, there's no way the mapping would work correctly if you try to use it with a previous version of SDL. We can add them here, but the triggers won't work correctly....and to fix that you have to update SDL, which again makes adding them here pointless.

from sdl_gamecontrollerdb.

Right, but I guess my question is whether “the buttons map and can be used, but the triggers don’t do anything” is more desirable to you than “this controller doesn’t work at all?”

from sdl_gamecontrollerdb.