- Feb 23, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Feb 22, 2017
-
-
Peter Hutterer authored
Easier to track if we leave the original files alone. Actual changes to the doxygen style: * indent <dd> blocks * hide the navigation sub-items. Our current style expands the full navigation menu but File-list, etc. is mostly useless and just wastes space. * force some space below the main bar * change the header sizes around a bit. Primary goal here: making <h1> smaller than the title Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
It was just floating around lonely there and I doubt anyone really used it. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Feb 21, 2017
-
-
Peter Hutterer authored
-
Peter Hutterer authored
The range that matters is 0-200, maybe up to 400 if you account for really fast movements. But to match other, published, accel curves default to up to 1000 mm/s. It's easy enough in gnuplot to reduce the range. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Missing from 8c1aa1de where we hid the human-readable parts but the keycode itself is still enough information to recover the typed bits. Print it as -1 as that keycode doesn't exist for real keys so it stands out nicely. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Feb 20, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This may be a feature for the future but for now be honest and don't claim that button-based scrolling is available, it's not hooked up in the absolute code path. https://bugs.freedesktop.org/show_bug.cgi?id=99865 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Before, our states were idle, button down and scrolling. This adds a state where the button is down and the timeout has expired (i.e. we're ready to send scroll events) but we haven't actually sent any events anymore. If the button is released in this state, we generate a normal click event. https://bugs.freedesktop.org/show_bug.cgi?id=99666 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
No functional changes, preparation work for adding another state. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
This is merely 'button scrolling' now, only the original implementation was middle button only. And to avoid confusing with the middle button emulation, drop "MIDDLE" from the define. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Device needs BTN_MIDDLE disabled, this way middle button emulation is present by default. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
This worked before, but triggered a negative timer bug. When one of the physical L/R buttons is pressed with middle button emulation enabled, the flow is: 1) phys left button down 2) middle button state machine discards events, sets timer 3) timer expires or button is released 4) middle button state machine sends button press with time from 1) 5) emulation code sees button press, sets timer for scroll emulation 6) timer logs bug because (original-button-time + timeout) is less than now() That log_bug_libinput() warning fails the tests but works otherwise. Allow this situation explicitly, on some devices we only have left and right buttons and no scroll wheel, so having middle button emulation *and* button-scroll working is useful. https://bugs.freedesktop.org/show_bug.cgi?id=99845 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
The button-scroll by default behavior is only true on devices with a middle button. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
And disable middle button emulation for this test, it would mess with the test results. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
This failed on devices without a middle button, we just didn't have a test device to trigger this. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
We don't have the same libevdev context that libinput has so if libinput disables/enables event codes we don't see that and may get unexpected behavior in the test. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Sub-mm precision isn't needed for libinput-list-devices' size field. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
This device has BTN_LEFT, BTN_RIGHT, BTN_FORWARD and BTN_BACK, add the missing range to the pad init function. https://bugs.freedesktop.org/show_bug.cgi?id=99785 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
- Feb 17, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Feb 14, 2017
-
-
Peter Hutterer authored
makes it easier to filter out debugging messages Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
- Feb 13, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
libinput-debug-events prints keycodes as they come in. This makes it dangerous to be run by users (especially in the background) because it will leak sensitive information as it is typed. Obfuscate the base set of keycodes by default, require a --show-keycodes switch to show it. The few times we actually need the keycodes, we can run the switch in the debugging tool. This does not affect keys outside of the main block on the keyboard (F-keys, multimedia keys). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
This will eventually feature the architecture diagrams, etc. But for now it's mostly just a list of what will be and what won't be supported. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Feb 12, 2017
-
-
Peter Hutterer authored
dwt is needed on internal touchpads only and those external ones that are a combo device. This also now gives us the same check for palm detect and dwt. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Specify the layout of the combo so we know when to initialize palm detection. This allows us to drop palm detection on external touchpads otherwise, replacing the wacom-specific check with something more generic.. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
- Feb 09, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Simplest implementation for what we need right now, it turns off an event on the evdev device and turns it back on again. This allows us to change bits in the 'normal' event stream, such as changing the tool type without triggering proximity events for the BTN_TOOL_PEN that all test devices send by default. This won't work for absolute devices because we need to re-enable with a struct input_absinfo. But we don't need that ability for now anyway. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
So we can test it externally. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-