From the top just, to get our way through this treacle, what a game wants is:
1. Enumerate input devices.
2. Select the HID type each player wants and get a device that
supports that usage.
e.g. Mouse type devices - (could be thumb-stick, pointer stick, mouse,
accelerometer, trackpad or pen as
On Sun, 2015-04-19 at 15:29 +0900, x414e54 wrote:
The way todo this seems to be for the compositor and client to
negotiate an event type they both can understand such as
libinput_event or hid events and then a way to request a revokable
fd to the evdev directly so it can control LEDS and
On 19 April 2015 at 06:15, x414e54 x414...@linux.com wrote:
On Sun, Apr 19, 2015 at 12:45 AM, Michal Suchanek hramr...@gmail.com wrote:
On 18 April 2015 at 16:58, x414e54 x414...@linux.com wrote:
A joystick does not necessarily have 2 axis and in most cases yes they
are reporting an
Hello,
It seems like this discussion died off. Currently there is no way to tell,
from the Wayland XML specification whether an argument is a bitfield, or
whether the argument takes an enum and what enum this is.
I am currently in the progress of writing a Wayland binding generator for
the Rust
This is sort-of legitimate, so simply disable the axes and continue.
Any real axis we require to have a real range.
https://bugs.freedesktop.org/show_bug.cgi?id=90090
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
src/evdev.c| 26 --
test/Makefile.am |
