Open travankor opened 4 years ago
Maybe. It's not something that is urgently needed I think, although I see why some would want this. If this is something you feel strongly about, open a PR and we can discuss details.
I don't think this is urgently needed either since you could install your own libinput with hardcoded settings. This works for people for embedded applications or one-off use cases, but it doesn't seem like a good solution for distros or broader use cases.
I don't know enough C or have enough general knowledge of wayland/libinput/wlroots to solve this now. I guess I would be willing to learn :)
Or maybe wlroot's should have a higher-level compositor-agnostic way to deal with this?
Any update on this? In our environment we use cage on notebooks with our custom kiosk application. It's very unintuitive for our users that taping does nothing. What would be the best way to enable this behaviour? Patching libinput as descriped or is there an easy way to enable taping in your code, so we can modify it for our use case?
In case this issue doesn't get resolved, here's a workaround - libinput-config.
How about enabling various input device option (like touchpad tapping) based on the values of environment variables? Minimal changes in the code and consistent with use of XKBDEFAULT* for keyboard settings.
I think I'll implement a patch that does this, then open a pull request.
I'd be happy to merge such a PR!
There should be a way to setup libinput settings, like how
sway-input
does, to set features like tap and dwt. Maybe have an env variable for the libinput settings and send that to libinput?