https://bugs.kde.org/show_bug.cgi?id=489746
--- Comment #6 from Grósz Dániel <groszdaniel...@gmail.com> --- (In reply to pallaswept from comment #5) > >see Fitt's law; if I just want an unmaximized window at the top of the > >screen, the target has infinite size if the automatic maximization feature > >is disabled, > > I can't reproduce this. If this feature is disabled, now we can drag the > window beyond the edge of the screen, so the target is not infinitely large, > it is infinitely small, because we have to hit that single row of pixels, > the top of the screen, in order to leave the window there. > > Of course, there's snap to edges, which would help us hit that row, but you > already can't hit that reliably and report accidentally dragging it too far, > and turning the 'maximize on top edge' feature off does not prevent that, it > just means that when you do drag it too far, rather than maximising, you > just drag it off screen. Neither setting it on or off can compensate for > dropping it in the wrong spot and give the result you wanted. You need to > not drop it in the wrong spot. If I'm dragging a window by its title bar, I can't drag it past the screen upwards*. That, combined with window snapping, means that with automatic maximization disabled, dragging a window upwards arbitrarily much puts it exactly at the top of the screen. * Except if there's another screen arranged above it. (I logically arrange my screens side-by-side for this and similar reasons.) But if there's another screen above it, the automatic maximization doesn't work either even if it's enabled, so that's another problem with the idea that if you want to maximize the window again, you can do it easily. > > but a smallish finite size if it's enabled. > > You can configure that size to be one that works for you, large enough to > avoid accidents. Where? With automatic maximization enabled, windows get maximized as soon as the mouse touches the top of the screen. In the Screen Edges kcm, where automatic maximization can be enabled, there are no setting to adjust that. The smallish finite size you need to hit to drag a window to the top of the screen when automatic maximization is enabled is about half the thickness of the title bar (the distance between where you grabbed it and its top edge) or the snap zone, whichever is thicker. The only ways to increase it is to use huge title bars (taking up space) or huge snap zones (at some point getting in the way of being able to freely arrange windows). > This is the same size defined here as "somewhat". You can make that "somewhat > larger" :) if it's too small for you, which, if you're doing things by > accident, it is. Where? I've not seen any settings related to this new automatic unmaximization feature. (It doesn't use the window snapping zone set in Window Behavior / Movement. The "somewhat" is actually bigger than the window snapping zone, but still small enough that I sometimes accidentally trigger it when dragging vertically maximized windows over a long distance between two screens arranged side by side. In the video I of course triggered it intentionally to demonstrate it, I'm more accurate usually, but I've occasionally triggered it unintentionally.) > You can rely on automatic snapping, or manual accuracy, but using neither and > hoping for a good result is hoping for a mind-reading computer. Give it a few > more years :D What I'd like is quite the opposite: don't maximize or unmaximize windows (fully or in one direction) unless I explicitly trigger it with the appropriate button/shortcut/double click, just like it behaved until recently. > > The behavior thus depends on not just the start and end points of the > > dragging, but the path the cursor takes between them > Suggests that maybe this would work better if only the end point were > considered. I feel like this is the trick, but going back to the start of > this message - maybe there is a use-case for considering the entire path? I > can't think of one. That would more-or-less solve it for vertically (or horizontally) maximized windows: if you accidentally unmaximized it by moving it vertically, you could still undo it by moving the mouse back to approximately the same vertical position as you started with before releasing it. Though I'd personally probably still slightly prefer vertically maximized windows to move but stay vertically maximized when moving them in any direction (a use case being to quickly move a window out of the way by dragging it in an arbitrary direction to see another window and possibly click something in it, and then moving it back); it's slightly weird that vertical maximization can be toggled in one direction by dragging a window but not in the other direction. For fully maximized windows, we could have them unmaximized as long as they stay on the same screen, but maximize them immediately if the cursor is dragged to another screen (regardless of where they are released), since that suggests that the user may have intended to just drag them to another screen without unmaximizing them, while there's no point in dragging within the same screen if you don't intend to unmaximize. Though that behavior could be seen as weird too. Another solution, of course, would be to allow turning the current, new behavior off as I suggested, either as a separate option or tied to the automatic maximization option. -- You are receiving this mail because: You are watching all bug changes.
