Re: [AD] Android Gamepads

I think we can drop Android 2.x support, by the time Allegro 5.2 is out there will hardly be any left. But if it's easy enough to use a different joystick driver for 3.1+ only, we should do that instead.

As for accelerometers, that can probably just be a joystick (with 3 or 6 axes). Things like a steering wheel or gas pedal or thrust control on a flight stick also would just appear as a joystick axis right now so in general we don't want a different event source for different types of axes.

On Mon, Sep 8, 2014 at 4:22 PM, Trent Gamblin <trent@xxxxxxxxxx> wrote:

For some reason, I guess because gamepads weren't common on Android/iOS,
those ports use the accelerometer for the joystick.

This is becoming a problem. On OUYA you can actually access the
/dev/input device for the joystick, but on other devices you can't. What
other devices? There's Fire TV, tablets with gamepads connected, SHIELD
and any time now (I have this confirmed) a Google console. Plus on OUYA
/dev/input isn't reliable because the "menu" button doesn't work.

So I'm proposing that we support real joysticks on Android instead of
accelerometer. It's a standard interface on Android that works across
all devices. However, it requires Android 3.1.

Accelerometer could be given its own event source if anyone can come up
with an API.

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
--
https://lists.sourceforge.net/lists/listinfo/alleg-developers