https://bugs.kde.org/show_bug.cgi?id=377309
--- Comment #14 from Nate Graham <n...@kde.org> --- David, you didn't address any of my arguments. I will be happy to address the new ones you introduced, and I hope you will take the time to do the same for mine. > If it looks like an icon it should behave like an icon. Icons do not have a set, predictable behavior. An icon is a visual symbol that is added to an interactive user interface element that supplies the behavior. For example, icons can be found on pushbuttons, menu items, list items, status indicators, and files or folders in a file manager. How these elements respond to clicks depends on the UI element itself, not the presence, absence, or appearance of an icon. Notably, Gwenview's thumbnail view respects the single/double click settings without having any icons whatsoever (it has thumbnails instead). The single/double click setting has nothing to do with whether the element looks like a file or folder in Dolphin. > A user approaching it doesn't know whether there's additional actions or not > when they're first mouse clicking. This is precisely why the traditional appearance of pushbuttons is actually buttonlike. The modern trend of making pushbuttons borderless is what generates this confusion. A button with an icon in it that actually looks like a button produces no confusion regarding what it is or how you're supposed to click it. Regardless, there's a simple solution to this issue that does not require changing the visual appearance of anything that's single-clickable: make the mouse cursor use a finger cursor when hovered over it. That's the entire point of the finger cursor: it says, "this will open something new or take you somewhere else when you click". It's a visual cue that was invented precisely to alleviate the potential confusion regarding how many times you need to click on something. -- You are receiving this mail because: You are watching all bug changes.
