Bug 62955 - double click "folded" in single click mode
Summary: double click "folded" in single click mode
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Stephan Kulow
: 58644 64294 (view as bug list)
Depends on:
Reported: 2003-08-19 12:31 UTC by Leo Savernik
Modified: 2005-03-17 21:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Leo Savernik 2003-08-19 12:31:07 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc 2.95.2 
OS:          Linux

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.
Comment 1 Stephan Kulow 2003-09-14 13:50:07 UTC
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? 
Comment 2 Leo Savernik 2003-09-14 21:12:15 UTC
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 
ok there. 
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 
coming through? 
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. 
Comment 3 Stephan Kulow 2003-09-15 19:34:06 UTC
*** Bug 64294 has been marked as a duplicate of this bug. ***
Comment 4 Stephan Kulow 2003-10-27 18:03:38 UTC
*** Bug 58644 has been marked as a duplicate of this bug. ***
Comment 5 Bugs Kde Org 2004-05-10 19:41:45 UTC
If QT sends a double-click, couldn't KDE just interpret this as two single clicks?
Comment 6 Dik Takken 2004-07-06 14:58:54 UTC
There is a thread about this problem on the usability mailing list:

Comment 7 Michael Jahn 2004-08-06 19:21:29 UTC
This works for me with 3_3_Branch. Can anybody still reproduce this with a recent KDE?
Comment 8 Dik Takken 2004-08-06 19:51:50 UTC
The problem with Konqueror's navigation buttons not responding to quick repetitive clicks has been solved in KDE 3.3 Beta 2. 
Comment 9 Leo Savernik 2005-03-17 21:04:54 UTC
Indeed, bug has been solved meanwhile.