Skip to main content
8 events
when toggle format what by license comment
Sep 15, 2020 at 0:11 comment added Matheus Portillo @sjy another way to answer is that there is already a absolutely ridiculous amount of libinput events being filtered out and scrolling as fast as you can probably wont be more than 10% of those, so if there was a performance issue, it would be in "trigger" part of mapping, not in the reading, and a better way of reading events wouldn't solve this. And the trigger part (cli command with evemu) is not the bottleneck when talking about any commom GUI event, so a better way to trigger wouldnt solve it too.
Sep 15, 2020 at 0:04 comment added sjy Thanks, I think I will give this a try! I notice that it is also available via the wayland-mouse-mapper-git AUR package.
Sep 15, 2020 at 0:01 comment added Matheus Portillo @sjy I reckon that extremely high frequency events probably wont skip but can stack, resulting in lag. It is specially likely to happen if you map it to a button that triggers something that does not handle repeated events. However, this problem happens in the layer outside mapping. There is for sure more efficient solutions of mapping, as reading SO binary input buffer, but if you do so you are still subject to the same thing. The point is that although there is more efficient ways, this is not the bottleneck (at least for common interface mapping).
Sep 11, 2020 at 7:29 comment added sjy Thank you for sharing this script! I see that it works by parsing the output of libinput debug-events. Has this been reliable in your experience? I am wondering if this could be used to handle high frequency scroll events or if a more efficient solution is needed.
Aug 10, 2018 at 14:45 review Late answers
Aug 10, 2018 at 14:50
Aug 10, 2018 at 14:41 history edited slm CC BY-SA 4.0
added 636 characters in body
Aug 10, 2018 at 14:30 review First posts
Aug 10, 2018 at 14:39
Aug 10, 2018 at 14:28 history answered Matheus Portillo CC BY-SA 4.0