https://bugs.kde.org/show_bug.cgi?id=377309
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|1 |0
Resolution|INVALID |---
Status|RESOLVED |UNCONFIRMED
--- Comment #7 from Nate Graham <n...@kde.org> ---
I feel like I may not be expressing myself very clearly here. Let me try again:
It only makes sense for something to be double-clickable if there are things
you can do with it when it's selected, but not yet open.
Changing the setting to double-click affects the behavior for clicking *files
and folders.* The purpose of using double-click when applied to files and
folders is to make selection easier, because files and folders have a lot of
things you can do with them once they're selected.
Changing the setting to double-click does *not* change the number of clicks
required to activate buttons or menus. This is because these UI elements never
need to be selected, and there is nothing you could do with them after
selection even if you could select them.
I am asserting that the icons in System Settings Icon mode have more in common
with buttons than they do with files and folders because they never need to be
selected, as evidenced by the fact that when double-click is set, they
erroneously *can* be selected, but there's nothing special you can do with
them. Ergo, it makes sense to treat them like buttons rather than files, and
always activate them with the first click regardless of whether single-click or
double-click is the click method for files and folders.
Does that make sense?
--
You are receiving this mail because:
You are watching all bug changes.
