Re: External monitors as "desktops"

Am Montag, 28. Februar 2022, 15:47:40 CET schrieb Aleix Pol:
> On Sun, Feb 27, 2022 at 4:42 PM Neal Gompa <[email protected]> wrote:
> > On Fri, Feb 25, 2022 at 5:55 PM Joshua J. Kugler
> >=20
> > <[email protected]> wrote:
> > > On Monday, February 21, 2022 2:31:43 AM AKST Thomas L=FCbking wrote:
> > > > Am Mon, Feb 21, 2022 at 10:28:42AM +0200 schrieb Vlad Zahorodnii:
> > > > >On 2/18/22 22:28, Joshua J. Kugler wrote:
> > > > >>Is there a way in kwin/plasma to make an external monitor its own
> > > > >>"desktop?" That is, when you hit "ctrl-tab" to change desktops, t=
hat
> > > > >>monitor does not change its display?  Similar to the way Mac (can)
> > > > >>handles external displays.>
> > > > >
> > > > >At the moment, kwin does not support per monitor virtual desktops,
> > > > >but
> > > > >there was an attempt to fix that.
> > > >=20
> > > > I major obstacle will be that this isn't covered by the NETWM spec =
and
> > > > you'll have issues reporting the current virtual desktop or treating
> > > > requests to move or move windows there.
> > > > So the implementation would probably have to exist aside that conce=
pt
> > > > and then is just some way to manage the mapping state of windows on
> > > > the
> > > > current (in doubt only) virtual desktop.
> > >=20
> > > As much as I would like to see KDE implement this, I'd much rather the
> >=20
> > spec
> >=20
> > > amended  than KDE break the spec and break interoperability with other
> >=20
> > apps
> >=20
> > > and desktops.
> > >=20
> > > Is there a ticket/proposal in front of the the Freedesktop group to a=
dd
> > > something like this? If not, how would one go about requesting?
> >=20
> > Does NETWM apply in a Wayland world? It and ICCCM are built on X11
> > specific stuff, so I suspect we can mostly ignore it for KWin on
> > Wayland.
>=20
> I imagine it would still affect for Xwayland clients (which is no small
> detail).

I don't think it's a problem for Xwayland client. The biggest concern I had=
 in=20
the past on X11 was that windows would not render correctly due to thinking=
=20
that they are not on the current desktop (e.g. video players pausing=20
automatically). In an XWayland setup we are basically always in a situation=
=20
where a window cannot know whether it is currently visible or not and it=20
doesn't create problems. Furthermore I have never heard of any problems in =
i3=20
with this.

>=20
> And yes, if this was ever implemented, it probably should be a wayland-on=
ly
> feature.

fully agree, that should be Wayland only.

Martin