<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Some way to inject automated libinput events?" href="https://bugs.freedesktop.org/show_bug.cgi?id=99800#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Some way to inject automated libinput events?" href="https://bugs.freedesktop.org/show_bug.cgi?id=99800">bug 99800</a> from <a class="email" href="mailto:ryan.hendrickson@alum.mit.edu" title="rhendric <ryan.hendrickson@alum.mit.edu>"> rhendric</a> <pre>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. <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - RFE: extra option to define the vdist/hdist for scrolling event" href="show_bug.cgi?id=92772">Bug 92772</a> 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).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>