https://bugs.freedesktop.org/show_bug.cgi?id=99079
Peter Hutterer <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #2 from Peter Hutterer <[email protected]> ---
(In reply to defree from comment #0)
> ## Problems
>
> Spurious KEY_F23 event when clicking (that is a single click produces mouse
> button + keypress events). (+ pad disabled notification)
if you see KEY_F23 then that's a hardware issue. something isn't initialized
correctly by the kernel, libinput doesn't generate those by itself.
> Clunky scroll:
> - not always detected
> - take time to start then scroll by one big chunk
>
> No tap and drag feature, this is critical for usability.
is the touchpad detected as a touchpad or just as a mouse-like device? If the
former, you'll have to enable tapping, libinput has it disabled by default.
an evemu-record of a scroll sequence should tell us what's going on there.
> # Touchscreen
>
> usb-id: 03eb:8209 Atmel Corp.
> libinput-name: Atmel Atmel maXTouch Digitizer
>
> ## Problem
>
> I am not familiar with touchscreen, so maybe the behavior I am about to
> describe is normal and the bug elsewhere.
>
> A sequence for a click is TOUCH_DOWN, TOUCH_FRAME, TOUCH_UP.
> During motion, every TOUCH_MOTION is interleaved with a TOUCH_FRAME.
yeah, that's correct and is the expected behaviour. TOUCH_FRAME is needed to
group frames. either way, short answer here is: touchscreen gestures like
tap-to-click is something that needs to be performed on the client-side, i.e.
in the application. recent GNOME3 should do this but otherwise it depends on
the toolkit.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
wayland-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
