If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
Uhm, it's not really new, I'm working on a project that uses it and it just works in Chromium 56, moreover, it's not standard controller but dance pad, detected as 10 buttons.
BTW, that API sucks, it provides only events for newly connected (or more like, only when they are used for the first time, reported as added only after pressing some button etc.) or disconnected devices, you have to poll it constantly to find out if button was pressed...
@lunarcloud, but it's not the only use case plus why do not have *both*?
You don't have to use events when they are available, you can keep polling, lack of them is really inconvenient when your use case doesn't require constantly running loop and you have to implement it just to add controller support.
Uhm, it's not really new, I'm working on a project that uses it and it just works in Chromium 56, moreover, it's not standard controller but dance pad, detected as 10 buttons.
libinput explicitly avoids dealing with gamepads. It's kinda hard to account every possible combination of gamepad "geometry". Latest related news were about creating inputfd protocol for managing gamepad access for apps, and letting app to do with the device whatever it wants https://who-t.blogspot.ru/2017/04/in...access-to.html
Comment