Re: On showing windows where the users want them, on wayland

David Edmundson <[email protected]>
Newsgroups gmane.comp.kde.devel.kwin
Message-ID <CAGeFrHA3dXyawZ7-59V6=4mAJNqo4ZCS3iz51=TCJypTtj8DPA@mail.gmail.com>
It depends on whether someone needs to recreate xeyes!

>- make Qt report the screen where the current cursor is the primary
one,

QScreen constantly changing would make plasma panels move, we don't want to
expose cursor pos that way.

>- include in the KWayland::Client::PlasmaShell a way to report the
screen (e.g. the edid or another identifier) with the current cursor.

We would probably use a wl_output ID as an arg.

Being in PlasmaShell is also potentially problematic.

You need this information before we show.
We don't have a wl_surface after the first hide() before the second show(),
which means we can't have a plasmashell.

It might be doable still, but that order needs thinking about before making
protocol mods.

-----

From a "pure wayland" POV, this approach is backwards - the client should
be specifying the position semantically then kwin would do its thing.
We have the client doing things in absolute positions to have a nice client
migration path from X. I hope to be changing that for KF6.

David
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.