https://bugs.kde.org/show_bug.cgi?id=357450
--- Comment #1 from Thomas Lübking <thomas.luebk...@gmail.com> --- @Martin, why is the timer started on release and checked on press? Afaiu mouseDoubleClickInterval(), it implies a full cycle, ie. you'll have to press (or rather release?) twice within this time to trigger a doubleclick action (resp. all singleclick actions are delayed by this time) So a press would start on an invalid timer and invalidate (and conditionally start) on a valid timer. Otherwise we'll have to carry the condition between press and release, but for now I wonder why they're split at all. Comparing eg. dolphin w/ enabled doubleclick, I can press, hoooooold, press, hooooold, ... w/o triggering something, ie. the time between release and press doesn't matter, but press, release, press, already to late for hooooold... ;-) -- You are receiving this mail because: You are watching all bug changes.
