Version: (using KDE Devel)
Installed from: Compiled sources
Compiler: gcc 2.95.2
In single click mode one expects to work everything with a single click. However, not every single click is actually regarded.
If you click twice on a toolbar button or kicker button within a short period of time, the second click is swallowed.
This seems to be done to "fold" double clicks into single clicks, for reasons I cannot imagine. But this is not only unnecessary, it is counter intuitive that the amount of clicks do not correspond to an equal amount of actions under all circumstances.
It is a usability nightmare being forced to wait between clicks because it interrupts the stream of work (or causes twice the works as one clicks for times instead of two, which is questionable from an RSI point of view).
No other GUI I had acquaintance with exhibits this strange "folding", not even the inherently double-click GUI of Wind*ws.
Furthermore, in KDE 3.0, double clicks were *not* "folded" on kicker buttons, that means clicking three times would start three instances of an application, just like commanded. They *were* "folded" on toolbar buttons, though.
I'd like to see a consistent single-click mode for KDE 3.2 that works as expected, and doesn't try to make up the mind for the user.
afaik it's even done in Qt. And you can configure the double click interval. But
what do you suggest how to differ between a single and a double click?
Well, for kicker, the problem has been solved. Two clicks (regardless how short
the timespan between them) will start two instances of the app. So everything's
However, toolbar buttons still eat the second single click. I think they should
*never* react on doubleclicks, handling all of them as two consecutive single
clicks (at least in KDE's single-click mode). You say it's a Qt thing, but
isn't there a possibility with which KDE can keep Qt from doing mischief? An
event filter on KDE toolbars perhaps that prevents double-click events from
I'm not aware of any (KDE) application that does a different action when
double-clicking a toolbar button instead of single-clicking, so there's no
actual need for a double-click.
*** Bug 64294 has been marked as a duplicate of this bug. ***
*** Bug 58644 has been marked as a duplicate of this bug. ***
If QT sends a double-click, couldn't KDE just interpret this as two single clicks?
There is a thread about this problem on the usability mailing list:
This works for me with 3_3_Branch. Can anybody still reproduce this with a recent KDE?
The problem with Konqueror's navigation buttons not responding to quick repetitive clicks has been solved in KDE 3.3 Beta 2.
Indeed, bug has been solved meanwhile.