I was imagining a trackpad that is not "smart" and somebody wants to
define a global hotkey to turn it off because they keep getting unwanted
events. The disable state would allow this to be done without rewriting
the trackpad driver.
My main point is I don't think you need to distinguish enabled from
"smart" enabled. The smartness is in the device driver and could be
considered part of how it generates events, and there should be no
reason to turn it off.
On 08/21/2014 07:54 PM, Peter Hutterer wrote:
On Thu, Aug 21, 2014 at 06:35:57PM -0700, Bill Spitzak wrote:
Seems to me you only need two states: what you call disabled and what you
are calling "smart disable".
The fully disabled is so a button the hardware does not know about can
disable the device. Or a wayland compositor could use a mouse being added to
disable the device.
the compositor doesn't know which device is a mouse, which devices are
virtual, or even if the touchpad is an external touchpad (which wouldn't
need that feature).
But the "smart disable" sounds like part of the device driver / libinput
driver, just like palm detection. There is no reason to turn it off. Maybe
to "tune" it but that would require a much more complex api.
_______________________________________________
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
