Clients need to know which methods are available, not just which one
is currently set. Export bitmask config options as two properties,
one read-only named "... Available" and one set-able one named "... Enabled"
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Clients need to know which methods are available, not just which one is
currently set. Export bitmask config options as two properties, one read-only
named "... Available" and one set-able one named "... Enabled"
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
If the driver doesn't have a pInfo reference anymore for a libinput device,
don't bother processing events, the device was already removed. This was
triggered by the libevdev test suite which adds/removes devices very quickly.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This currently exposes the libinput button name, which isn't ideal. Needs to
be switched to X button numbers.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Let the server filter based on the verbosity levels in the server, so map
ERROR to -1 (always), INFO to 3 (default verbosity) and DEBUG to 10.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This only makes room for the highest button number present on the device, it
doesn't cater for devices with 'holes'. i.e. if a device has only BTN_BACK, it
will initialize buttons for all below too.
Which is also evdev's current behavior.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Less code this way, though if we somehow sneak in a bad option we get the
error for it every time we update any property.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
The property support isn't ideal, the server relies on the driver to check
first if a setting is possible, applying the setting itself cannot fail.
Thus we can't just check the libinput config status code, which matters mostly
in the sendevents property where we simply check that only a single bit is set
and that the supported modes are equal or more to the requested mode.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Once we turn the device off, we may still get events from it but the pInfo
struct may not be valid anymore to process those events.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Allows us to use subpixel data, not that the server does a good job with it.
But at least for scrolling we should now be able to scroll by small amounts
too.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
