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.
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
