Thank you very much, I will discuss this idea with the designer.
I'd like to ask, why the underlying device is not exposed in
current wayland-protocols, what are the benefits of doing this.
With keyboard and pointer, we don't usually care about
physical device, but for touch devices, each touch
s a bit of a mindshift - think of Wayland like HTTP. You
don't configure your browser via HTTP requests from the websites, that
is done through other channels, for a whole bunch of reasons.
Cheers,
Peter
> At 2023-11-24 09:11:34, "Peter Hutterer" wrote:
> >On Wed, No
