After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 647062 - [Patch] Nautilus ignores consecutive double clicks in icon view
[Patch] Nautilus ignores consecutive double clicks in icon view
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: Views: Icon View
2.32.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-04-07 16:39 UTC by Tanyel A. Nimeu
Modified: 2011-04-07 18:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Proposed (quick&dirty) patch (648 bytes, patch)
2011-04-07 16:39 UTC, Tanyel A. Nimeu
none Details | Review

Description Tanyel A. Nimeu 2011-04-07 16:39:56 UTC
Created attachment 185441 [details] [review]
Proposed (quick&dirty) patch

Overview:
Two (or more) consecutive double clicks in icon view are only recognized as a single double click.

Expected result:
A "quadruple click" should trigger two double clicks.

Actual result:
Only the first double click is recognized.

This is especially annoying when trying to traverse fast through several directory levels. To better illustrate my problem, here are the

Steps to reproduce:
in Terminal:
$ cd $TMP
$ mkdir -p level1/level2/level3
$ nautilus level1
Now in nautilus:
- change (if necessary) to icon view
- position the mouse over the directory "level2"
- after double clicking and cd'ing in "level2" the mouse now is over "level3", so one can immediately proceed with double clicking on "level3" to enter it.

But what actually happens:
The first double click is recognized => one enters "level2", but any further double clicking is ignored until one pauses for a second...
So - without pausing - one could infinitely click on "level3" without entering it.


Fun facts:
This behavior was introduced with commit 0b74fe334f9c5b5353f8447df977470d13e73dd3 (so "it's not a bug, it's a feature", but a quite annoying one though).
What this commit does is ignoring any following clicks so that a triple click doesn't trigger two double clicks. But it also ignores any following intended double clicks.

Solution:
Quick and dirty: Reset the click_count after a double click, so subsequent double clicks are recognized correctly. (see attached patch)
Comment 1 Cosimo Cecchi 2011-04-07 18:33:56 UTC
Hi Tanyel; thanks for tracking down this bug, I experienced it myself a couple of times.
I committed a slightly different patch to git master. Closing as FIXED.