| Summary: | If the drag&drop delay=0 then double click to maximize a window does not work | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | extraltodeus |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | bshah, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | git master | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
extraltodeus
2015-11-17 17:37:43 UTC
It says "Drag start time" not drag and drop delay. (maybe a translation issue?) Kwin uses this setting to know if you're trying to drag the window. If you set it so that it should drag the window immediately, it will. Notice that no, we cannot rely on the drag distance setting (caused bugreports and looks "slow", changed in some KDE 2 release to move instantly) nor involve the doubleclick interval (since that can be rather long and the two dead times have no actual relation as the doubleclick is defined by the second click)
Why do you try to set the drag start time to 0 itfp, looking for the opposite ("never", not "instant")?
|