Hi,
I agree with Chad's suggestions: the spec should be expanded to expose
more than the core set of axes buttons, and richer metadata would be
extremely useful to developers.
I've been using the gamepad API (as shipped in Chrome, at least - I
haven't had time to adapt to Firefox's
Hi all,
I recently was asked to review the Gamepad API draft specification. My
background is games though I've done some scientific computing with
alternate input devices too.
http://chadaustin.me/2014/10/the-gamepad-api/
I'd like to suggest two simple changes to the Gamepad API. In tandem,
Re: change #1, with standard gamepad mappings today (at least in Chrome) we
map any buttons that don't correspond to the official standard mapping to
button[17] and up. This, of course, depends on which buttons are actually
visible to the browser (many devices expose buttons that can't be seen by
On Mon, Oct 13, 2014 at 3:55 PM, Brandon Jones bajo...@google.com wrote:
Re: change #1, with standard gamepad mappings today (at least in Chrome)
we map any buttons that don't correspond to the official standard mapping
to button[17] and up. This, of course, depends on which buttons are
