On Thu, 6 Nov 2014 05:36:32 +
"Zhang, Xiong Y" wrote:
> >
> > On Fri, 17 Oct 2014 12:37:37 +0300
> > Imran Zaman wrote:
> >
> > > In a multi-seat configuration, clients may need to filter out the
> > > outputs based on the (udev) seat it is hooked to or based on the name
> > > of the outpu
>
> On Fri, 17 Oct 2014 12:37:37 +0300
> Imran Zaman wrote:
>
> > In a multi-seat configuration, clients may need to filter out the
> > outputs based on the (udev) seat it is hooked to or based on the name
> > of the output.
> > Since version of the output is increased, the change does not affec
For future reference, wl_seat is actually more similar to the "MPX"
extension for X11, which allows for multiple pointer/keyboard pairs on the
same output seat. The only usecases I'm aware of for MPX are display walls
and multiplayer game cabinets.
On Wed, Nov 5, 2014 at 11:37 AM, Imran Zaman wro
Pekka, thanks a lot for the detailed explanation. Lets see which way we go.
BR
imran
On Wed, Nov 5, 2014 at 6:32 PM, Pekka Paalanen wrote:
> On Fri, 17 Oct 2014 12:37:37 +0300
> Imran Zaman wrote:
>
> > In a multi-seat configuration, clients may need to filter
> > out the outputs based on the
On Fri, 17 Oct 2014 12:37:37 +0300
Imran Zaman wrote:
> In a multi-seat configuration, clients may need to filter
> out the outputs based on the (udev) seat it is hooked to or
> based on the name of the output.
> Since version of the output is increased, the change does
> not affect the current i
In a multi-seat configuration, clients may need to filter
out the outputs based on the (udev) seat it is hooked to or
based on the name of the output.
Since version of the output is increased, the change does
not affect the current implementation and is optional whoever
wants to use the properties