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
---
src/evdev.c| 26 --
test/Makefile.am | 1 +
test/device.c
Well clearly gmail does line wrapping, which I did not realize. So
while I figure that out, please enjoy the patch which I attached.
On 19 April 2015 at 22:30, Auke Booij wrote:
> On 19 April 2015 at 14:51, Jeroen Bollen wrote:
>> Hello,
>>
>> It seems like this discussion died off. Currently th
On 19 April 2015 at 14:51, Jeroen Bollen wrote:
> 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 p
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 l
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 LED
On 19 April 2015 at 06:15, x414e54 wrote:
> On Sun, Apr 19, 2015 at 12:45 AM, Michal Suchanek wrote:
>> On 18 April 2015 at 16:58, x414e54 wrote:
>>
>>>
>>> A joystick does not necessarily have 2 axis and in most cases yes they
>>> are reporting an absolute position of the axis in the driver bu
