https://bugs.kde.org/show_bug.cgi?id=377309
--- Comment #15 from David Edmundson <k...@davidedmundson.co.uk> --- >you didn't address any of my arguments. >1. A thing that is not mouse-selectable (e.g. a toolbar button) should always >activate with a single click even when using the double-click setting Whether it's mouse selectable (and FWIW it is mouse selectable) or not isn't relevant, what's relevant is expected action. Like how we write "..." at the end of menus and buttons that will spawn dialogs. Users learn patterns. If something looks like something familiar, it should always behave like that familiar thing. Standalone icons in a grid in a frame should behave like standalone icons in a grid in a frame. There's no indication as to whether there's additional actions. You need that visual clue. And yes you could do it with a hover hand mouse over, but that's coming up with a solution for something that has yet to be shown is a problem. > 2. The double-click exists because some people prefer for the first click on > a mouse-selectable item to select it rather than open it. That's guessing, the only thing we know is a user has gone explicitly out of their way to turn this on. Copying the response in #10, it could be for: 1) reject click-through (with an eye to accessibility) 2) reduce the clickable area of a icon so that there's ample whitespace for a click to focus the window without activating a KCM 3) swallow the second click of a double-click so as to avoid activating something in the KCM that the first click activated 4) ensure that keyboard navigation works correctly so that one doesn't have to click in the icons view in order to reach the desired KCM icon > 3. A thing should only be mouse-selectable when there are actions besides Basically covered in 1. -- You are receiving this mail because: You are watching all bug changes.
