Summary: | Increase drag distance/time or use global value for quick maximization | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Micah Abresch <abresch> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | wishlist | CC: | thomas.luebking |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Micah Abresch
2010-05-29 22:37:49 UTC
please uncheck "Maximize windows by dragging them to the top..." in the "Screen Edges" page of kwins config dialog (rmb any titlebar, "configure...") and see whether the problem remains. do you use a notebook/touchpad? I didn't even know that option existed. As it turns out, that does solve the problem. So, an easy-to-work-around bug. Thank you very much. (and no, I do not use a notebook/touchpad) it however seems you're triggering a move - do you feel that happens to easy? (that's why i asked about the touchpad - most of them are -frankly- crap ;-) Yeah, I'm using a regular optical mouse, so it's not just that I'm working with a crappy input device. Yes, it's now clear that it's triggering a move, and after a little testing with that option turned back on, I'd definitely say that it's happening far too easily. I see no visual indication of motion whatsoever. I am not clicking-and-dragging, just using one quick click, so the behavior is very unexpected. Watching closely while doing this several times, it becomes clear that it happens no matter how little I actually move the cursor. If it is adjusted by even a single pixel while I am clicking, this happens, and that's just easy to do accidentally. It seems like the sort of thing that should have a threshold, like at least 5 pixels or at least a half of a second of holding down before it tries moving the window, but I have no idea how much trouble that would cause to other use-cases. "kcmshell mouse" / "advanced" check "drag start time" and "start distance" ... forget - the value is apparently ignored *** This bug has been marked as a duplicate of bug 222100 *** |