| Summary: | Moving the mouse while clicking an entry in the taskbar starts drag instantly (usability) | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma4 | Reporter: | Alex Dănilă <alex.danila.web> |
| Component: | containment-panel | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | cfeck, joao.vidal.silva, rndbit |
| Priority: | NOR | ||
| Version First Reported In: | 4.11.11 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Alex Dănilă
2015-07-05 03:13:37 UTC
I am not an old person and i start dragging taskbar items too often. This is very annoying. Worse yet something causes icon to "stick" to the mouse cursor even when left mouse button is released. Then i have to go all the way back to put icon where it was. Happens very often even on Plasma 5. My wife is always complaining to me, so please kindly fix this :D Could you please check if increasing the Drag Start Distance in systemsettings5 > Input Devices > Mouse > Advanced makes a difference? That setting makes a difference for a regular left-button-stays-pressed drag. But the 'funny' thing going is that the drag operation stays locked, as rndbit@nm.ru noted, with the icon having a plus sign (I'm using Breeze icons, in case that matters). I don't even know how to consistently reproduce this. So my result for the test you suggested is ambiguous. Christoph Feck - indeed, increasing that drag distance has an effect and mostly solved it for me (20 pixels isn't really that much on these high PPI laptops). João Vidal - I've only seen the "locked drag" with a laptop's touchpad, never with a mouse. This behaviour is so elusive. Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham |