[Wayland-bugs] [Bug 99800] Some way to inject automated libinput events?
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Feb 15 18:56:34 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=99800
--- Comment #5 from rhendric <ryan.hendrickson at alum.mit.edu> ---
Hm, okay. Your caution seems justified, even if I still think that there's a
use case for generating events that do look the same to the compositor as the
events that libinput/hardware would generate. But I'll focus my efforts on
implementing a hook in a compositor instead of at libinput and see whether the
concerns you're highlighting come into sharper focus for me.
Bug 92772 doesn't seem to be relevant, because that's about changing how
libinput generates events from hardware that it already recognizes, whereas
libinput explicitly ignores joysticks and gamepads (and I don't think I would
advocate changing that, given that I would want a joystick-to-input layer to be
very dynamic and configurable--it makes more sense to me for an independent
process to handle such nonstandard input hardware, a process that users can
start and stop and reconfigure and replace without disrupting their compositor
session).
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-bugs/attachments/20170215/5ab66e3c/attachment.html>
More information about the wayland-bugs
mailing list