"Disable while typing" is a great invention if you can't do proper touchpad palm rejection for whatever reason.

So why don't we have proper "disable while typing"? Every system with DWT seems to assume that "keys being pressed = typing". That means it completely breaks most games. Why can't games tell the system, "hey I'm a game, when the user presses keys while I'm in focus they're not typing"?

#programming #gamedev #laptops

Related: does anyone know if there's a way to make palm rejection work under #GNOME? The #libinput documentation (https://wayland.freedesktop.org/libinput/doc/latest/palm-detection.html) claims that it can do palm rejection, but it doesn't say anything about how I can influence it as a user. On this laptop, there's seemingly no attempt what so ever at rejecting accidental input from the palm

#linux #wayland

Palm detection — libinput 1.31.0 documentation

It's not quite the same, but someone in IRC recommended trackpad-is-too-damn-big (titdb): https://github.com/tascvh/trackpad-is-too-damn-big. It implements palm rejection as a separate daemon and works really well!
@mort I don't have an answer, but I feel your pain. I have a folding junker laptop that I've mused about trying certain games with for the touchscreen input. The keyboard is exposed and in the way after folding, which was the biggest hurdle at the time. It sounds like this is still an issue?