fix: support odd axes number

[FezVrasta]

This makes the code work in case gamepad.axes.length is 1 or any other odd number. It will round it up to the closest integer as expected.

[FezVrasta]

@Tom32i any chance you could take a look at this PR please?

[Tom32i]

Hey sorry I didn't see the notice :(

Thank you for the fix, Is it still relevent?

[FezVrasta]

Yes definitely

[Tom32i]

This means there is gamepads with 1 dimentional sticks?

[FezVrasta]

In our case it's a dictaphone, not a gamepad, but it gets exposed to the browser through the gamepad API.

[Tom32i]

Looks good to me. This makes me think maybe we should not expect axes to come by pair here.🤔

In your case, you're emulating a gamepad with only one axis that's right?

[FezVrasta]

I'm not emulating it, it's a peripheral that is recognized as gamepad.

[Tom32i]

Oh ok awesome. And you can confirm that your device only have one axis?

[FezVrasta]

I don't have access to it as it was reported by some customer, but I'm sure it reported a single axis. I suppose it was some kind of stick to allow scrolling up/down

[Tom32i]

Ok, that make sens. I'm gonna merge this PR. After that, I'll work on a small refactoring for a more clean support "odd" number of axis.

[Tom32i]

Do you need a new npm version with that fix?

[FezVrasta]

It'd be useful, thanks

[Tom32i]

Here you go, v1.0.5 is available :)