Ok, I got your point... So having both looks like the best option to me.
2014-11-10 10:15 GMT-02:00 Daniel Dressler :
> I'd love to make all controllers report as axises but doing so _will_
> break stuff downstream. Not least of which being every game which uses
> SDL2's controller configs:
> http
I'd love to make all controllers report as axises but doing so _will_
break stuff downstream. Not least of which being every game which uses
SDL2's controller configs:
https://github.com/gabomdq/SDL_GameControllerDB/blob/master/gamecontrollerdb.txt
Which is just about every-single major commercial
I totally agree that the behavior should be exactly the same in all
XBOX gamepads. But In my opinion this should be mapped as axis only,
since mapping for both could make a confusion in some games.
If you need the axis to be buttons, you can set as a option while
loading the module.
2014-11-10
Thanks Jon
I've sent a second version of the patch without the TODO list edits.
Now I would like to ask about a backwards compact issue related to this driver.
Eons ago in patch 99de0912b [0] when support for the wireless 360
controllers were added the decision was made to map their Dpad to the
On Mon, 3 Nov 2014 17:53:06 +0900
Daniel Dressler wrote:
> The last time this documentation was accurate was
> just over 8 years ago. In this time we've added
> support for two new generations of Xbox console
> controllers and dozens of third-party controllers.
>
> This patch unifies terminolog
The last time this documentation was accurate was
just over 8 years ago. In this time we've added
support for two new generations of Xbox console
controllers and dozens of third-party controllers.
This patch unifies terminology and makes it explicit
which model of controller a sentence refers to.
6 matches
Mail list logo
