https://bugs.kde.org/show_bug.cgi?id=489746
--- Comment #8 from pallaswept <pallasw...@proton.me> --- Let's try this again.... OP reported this problem: > need to manually maximize the window again. This sucks and we all agree this sucks and is a problem. Operative word: > manually The problem is the unnecessary requirement for manual intervention. In natural terms: "Maximise, move, maximise again" Sucks. We want: "Maximise, move" and then.... *do nothing, because it's still maximised?* Right? Right?? Wrong. This is where this conversation departed from our intention. We only really care about: "Maximise, move" and then.... *do nothing*. That last part above, "because it's still maximised", is just one imagined means to the end. And it's not a good one. In fact, sometimes we (KDE users, obviously none of you specifically) specifically want the availability of: "Maximise, move" and then.... *do nothing, because it's *not* still maximised, it's in some other state we just chose on purpose, during the move* If a solution does not accommodate that, it's not any good. It would break more than it fixes. OP asked for this solution: > windows should preserve their maximization status when dragged to a new > screen This is not the way to fix that problem. This is focussing on "still", not on "do nothing". We don't care if it's "still" maximized. We care if we have to "do nothing". If we force "still maximised", we fix one thing, and break several others. What if we want to drag a maximized window into a tile on the other screen? What if I want to drag my partially maximised window to fully maximized? Maybe I have something tiled to the left side and I want to move it to the centre now...Or back the other way? What if I start doing one thing and then change my mind? Now for every one of those (and many more), the maximisation state has been preserved, which was, to quote OP > not what I want and I have to > manually "do something" after the move, and they all are problems that suck just *exactly* like this does. But now there are *more* of them. That 'solution' only makes things worse. It doesn't resolve this problem, it multiplies it, and spreads it to everyone. I don't actually believe it is anybody's intention to basically say "this sucks for me, so fix it for me, and make it suck for everyone else", but that's what's been happening here so far. We all have lightning-fast moves that leverage Fitts' Law to provide ease of use, right now. Preserving maximisation state during moves, breaks that. It's not viable. It's just not. That doesn't mean give up, or leave it broken, it means we need to find something else. It seemed like a good idea, we looked closer, we see that it is a bad idea. Let's move on from that idea, so we can find one that does work. -- You are receiving this mail because: You are watching all bug changes.
