Summary: | double click "folded" in single click mode | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kdelibs | Reporter: | Leo Savernik <l.savernik> |
Component: | general | Assignee: | Stephan Kulow <coolo> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bugs.kde.org, davidsmind |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Leo Savernik
2003-08-19 12:31: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? 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. *** 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: http://lists.kde.org/?t=108902661800004&r=1&w=2 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. |