https://bugs.freedesktop.org/show_bug.cgi?id=90652
--- Comment #6 from Arun Raghavan <[email protected]> --- (In reply to Peter Hutterer from comment #5) > bit difficult, tbh. I try to add things like that in the release notes and > blog about it (I have an post pending for exactly that feature, just waiting > for 0.16 to be ready). And they're documented > (http://wayland.freedesktop.org/libinput/doc/latest/tapping.html). It's not > possible for anyone else in the stack to expose these, those features aren't > directly exposed. e.g. you can enable/disable tapping, but tap-to-end-drag > is built-in, you don't get to decide on it. > > If you want to bulk up the libinput documentation be my guest, I always > welcome documentation patches. I didn't meant to imply this belongs to libinput. With a one-time downstream hat, and current user hat, I definitely appreciate the changelogs and blog posts. >From the point of view of non-technical users, I was wondering how these things can be communicated. I think the responsibility will have to lie with distributions or with GNOME/KDE/..., as they are the closest to the user, and control when/which version of libinput is deployed. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ wayland-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
