| Summary: | Handling of fully included screens in clone setups with partial clones needs to be improved | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Aleix Pol <aleixpol> |
| Component: | xrandr | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version First Reported In: | 4.95.0 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Set up image | ||
|
Description
Aleix Pol
2014-04-10 15:41:14 UTC
Created attachment 86033 [details]
Set up image
I'm using a similar setup in daily productive work and don't have such issues. A few things to try: * is that also happening with non-Chromium windows? * how does it look if you kill plasma? seems a cloned/overlapping setup - can't test atm, but the maximize area will be calculated for the "wrong" screen. what if you move the unmaximized window so that 50% are on the non-overlapping region of the bigger screen? Martin: - It does happen with konsole and systemsettings too. On the other hand, I must say that depending on where the screen is, it uses the bigger size. - Same thing happens without a plasma Thomas: - Yes, it seems to use the correct size Raises the question why a client would reasonably be considered on fully included screens. - wanted partial maximization (poor mans tiling: "i keep my toolwindows on the free part"; projector case: "demo on both, text on mine only") - impact on currect screen estimation (where do new windows popup and does one really want to restrict that area / maximum size?) An alternative solution might be two-step maximization (maximize - maximize more - restore) btw, the bigger screen is the secondary one, right? Tried making it the primary? |