https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #14 from leftcrane ---
I think a shortcut or trigger to move all windows to primary is simple enough
to work as advertised. But it's your call obviously.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #13 from Martin Flöser ---
I'm pretty much against shipping solutions which cannot work. Sorry. We cannot
get that right for the reasons I mentioned and we won't start providing
solutions which will break in other parts. That's exactly what
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #12 from leftcrane ---
I "fixed" it on my end by writing a script that sets/unsets a kwin rule forcing
all windows to monitor one. Pretty crude and has to be run as hotplug, but it
gets the job done.
KDE should consider should consider
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #11 from Martin Flöser ---
I'm not sure, but it's common to make windows invisible by giving them a
geometry in the negative coordinates.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #10 from leftcrane ---
Yeah, I've looked into this and it seems like this is native behavior for X11.
So there is no way to set the origin elsewhere? It always has to the be in the
left corner?
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #9 from Martin Flöser ---
KWin doesn't know and doesn't care about primary monitors. It's not a concept
for window managers. Primary monitor has zero influence on placement of
windows.
The windows "move" because they have a position of
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #8 from leftcrane ---
(actually no that won't work with window snapping. so you'd have to make sure
the primary is always leftmost horizontally, regardless of how the monitors are
actually positioned on your desk).
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #7 from leftcrane ---
Either that, or just change the setup to make sure the primary monitor is
always in a specific position in the grid. So if you have three monitors
horizontally, you'd actually have to arrange them vertically with the
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #6 from leftcrane ---
Sorry to nag, but why can't the origin be located on the primary monitor?
Right now I have to move all the windows back to the primary monitor manually
after I connect a secondary, because most of them shift. That's
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #5 from Martin Flöser ---
Also on Wayland windows don't know their own position in global coordinates and
cannot move themselves. Given that we can keep them on the screen they are on
when changing the global coordinate system.
As David
https://bugs.kde.org/show_bug.cgi?id=405807
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
--- Comment #4
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #3 from leftcrane ---
Is it different in Wayland, btw? If you connect a secondary monitor, will your
coordinates also shift and cause windows to move to the left?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405807
--- Comment #2 from leftcrane ---
Is there something in X11 that necessitates this? Why can't the origin be
located on the primary monitor (instead of whichever monitor happens to be on
the left)?
I don't agree that nothing is wrong. Nobody wants all
https://bugs.kde.org/show_bug.cgi?id=405807
Martin Flöser changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Severity|normal
14 matches
Mail list logo
