Summary: | entering a directory causes a click blocking | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Ted <ted-> |
Component: | view-engine: general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | nate, teod0r |
Priority: | NOR | Keywords: | usability |
Version: | 2.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Ted
2012-04-21 15:31:32 UTC
Thanks for the report, but I cannot reproduce the issue with the 2 steps mentioned above. Do you probably have further information how to reproduce this issue? don't move the mouse after the first click and then quiqly make the second click also there is another bug: a blind spot (1 pixel width) between file's icon and file's name (4.8.2) but on another machine (4.4.5) there is no such bug Thanks for the hint - the next click must be inside the double-click timeout. If you speak from several seconds it might be that you use an extremely long duration for the double-click. But of course this should be fixed... could it be somthing not just only in dolphin? working in my old 4.4.5 I sometimes have a feeling that there is some kind of a same thing in othe applicatiions: when starting gtk version of firefox - firefox changes it's position from maximizet to minimized; clicking on "application launcher" on default_bar always waits for some period to second click; "show desktop" widjet in the corner of a screen shizoidly repeats always [ in 4.8.2 TOO!!!!! ( ]. maybe it something with kwin? render or somrthing? Resetting assignee to default as per bug #305719 @Ted: can you confirm Peter's assumption that the cause of the problem is that you have configured an extremely long double-click delay in the System Settings? (In reply to comment #7) > @Ted: can you confirm Peter's assumption that the cause of the problem is > that you have configured an extremely long double-click delay in the System > Settings? Most likely yes, but not an extremely long, I've set zero seconds I can reproduce, but when I set the double-click interval to 100ms, the issue disappears; it's practically impossible to click faster than that when the content is changing and your eye needs to scan what it is. |