Version: (using KDE 4.2.0) OS: Linux Installed from: SuSE RPMs Lately only double click on the icon opens a module in Systemsettings despite that my system is set to single click.
Which widget style are you using?
I use Plastique. Now I checked it with the styles on my system: the bug occurs with Plastique, Windows, Cleanlooks, Phase, Motif, CDE but does not occur with Oxygen, Bespin, QtCurve, Skulpture, Polyester.
Styles provided with Qt (Plastique, Windows, Cleanlooks, Phase, Motif, CDE) don't follow this kind of KDE setting, thus what you configure as single/double click mode cannot apply to them. If you want KDE settings (like this) to be respected, you have to use a style that uses the KDE facilities (like Oxygen).
Well, where doesn't it respect this setting? In Dolphin single/double click works as set regardless the style. And the default should be single click as that is the KDE default, shouldn't it? Shoouldn't KDE subclass the Qt styles so that they respect KDE settings? (AFAIK Plastik was a KDE style in 3.x so it is a regression if now it is not a well-behaving KDE style.)
(In reply to comment #4) > Well, where doesn't it respect this setting? Plastique is a Qt-only style, that is provided with Qt. > In Dolphin single/double click works as set regardless the style. That could be Dolphin working around the issue. > And the default should be single click as that is the KDE default, shouldn't it? Again: Plastique is a *Qt* style, not a KDE one, so it generally does nothing with KDE defaults. > Shoouldn't KDE subclass the Qt styles so that they respect KDE settings? And then what? If you choose a Qt only style anyway, you have the same problem. > (AFAIK Plastik was a KDE style in 3.x so it is a regression if now it is not a well-behaving KDE style.) Plastik was a KDE style in KDE 3, Plastique is a Qt style in Qt4.
I suspect Dolphin doesn't simply use a Qt list view/icon view class but has its own subclass, or draws the view on its own. Systemsettings could subclass the Qt widget in a similar way, deciding whether an icon is activated depending on the KDE setting. I think KDE shouldn't rely on the widget style respecting the setting because then Qt only styles don't work; it should have a subclass of the Qt list/icon view class which respects the KDE setting when deciding whether an icon is activated.
The reason why the behavior is unexpected and confusing and wrong does not make it invalid... this bug is related to: bug 193991