Re: Re: 回复: Re: get input device in wayland

2023-11-24 Thread Peter Hutterer
On Fri, Nov 24, 2023 at 11:00:34AM +0800, weinan wang wrote: > Thank you, I think I understand why the wayland-protocol is designed > the way it is. > Finally, I would like to ask if there is a input mapping protocol upstream is > considering to add like "xinput map-to-output". > Tablet, touch scre

Re:Re: 回复: Re: get input device in wayland

2023-11-23 Thread weinan wang
Thank you, I think I understand why the wayland-protocol is designed the way it is. Finally, I would like to ask if there is a input mapping protocol upstream is considering to add like "xinput map-to-output". Tablet, touch screen, and other absolute device mapping functions are currently imp

Re: 回复: Re: get input device in wayland

2023-11-23 Thread Peter Hutterer
On Wed, Nov 22, 2023 at 06:52:47PM +0800, WeiWei wrote: > 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. The overwhelmingly vast majority of applica

回复: Re: get input device in wayland

2023-11-22 Thread WeiWei
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