On Thursday August 10 2017 17:15:20 Martin Flöser wrote:
> Point is: if the kernel could read the information from the device, it
> would know it. I don't think that the kernel knows it, which means I
> don't think that the device driver has that.
Hmm. That still might make sense for position
Am 2017-08-10 01:45, schrieb René J. V. Bertin:
Martin Flöser wrote:
Hi
of the buttons, but just sends the press events. I'm pretty sure that
not even the kernel knows it, otherwise libinput would expose it.
It doesn't need to know it (and probably shouldn't because why would
it). All it
Martin Flöser wrote:
Hi
> of the buttons, but just sends the press events. I'm pretty sure that
> not even the kernel knows it, otherwise libinput would expose it.
It doesn't need to know it (and probably shouldn't because why would it). All
it
needs to know is how to read the information
Am 2017-08-05 17:23, schrieb René J. V. Bertin:
David Edmundson wrote:
In wayland you never query anything, only track events.
There are applications for which this isn't good enough but I guess
there must
be other, low-level ways to query the current state of a given input
device or
David Edmundson wrote:
> In wayland you never query anything, only track events.
There are applications for which this isn't good enough but I guess there must
be other, low-level ways to query the current state of a given input device or
sensor.
> What actually do you want to do?
I'm toying
In wayland you never query anything, only track events.
What actually do you want to do?
