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 347423 - double-click doesn't open half-shown items
double-click doesn't open half-shown items
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: Views: Icon View
2.23.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 373181 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-07-13 16:15 UTC by Sebastien Bacher
Modified: 2008-06-29 10:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Attachments
Patch for Bug 347423 – double-click doesn't open half-shown items (2.89 KB, patch)
2007-11-03 17:24 UTC, Nelson Benitez
rejected Details | Review
Patch implementing cneumair guide to fix this bug :) (2.52 KB, patch)
2008-04-21 01:21 UTC, Nelson Benitez
none Details | Review
Updated patch (2.67 KB, patch)
2008-06-26 11:14 UTC, Nelson Benitez
committed Details | Review

Description Sebastien Bacher 2006-07-13 16:15:42 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/52606

"I don't know how to make myself clear, but when an item is not fully shown in a Nautilus window clicking on it shows it... but double-clicking doesn't open the file. I'll attach a couple screenshots to explain it graphically.

http://librarian.launchpad.net/3342264/Pantallazo-tame.png
screenshot

http://librarian.launchpad.net/3342269/Pantallazo-tame-1.png
screenshot2
...
> Thanks for your bug report. Which version of nautilus and Ubuntu do you use? In Edgy the "half shown" file is focussed and shown fully, when I double-click it - another double-click opens the file. Is that the issue you see yourself?
...
I'm using Nautils 2.14.1 on Dapper. And yes, that's the behavior I'm getting too: If I click or double-click a "half-shown" file, it gets fully shown. Only then can I launch it by double-clicking again.

I'm not sure if this behavior is a bug or a feature, but I at least find it rather annoying."
Comment 1 Nelson Benitez 2006-07-15 22:42:47 UTC
I think this bug is annoying for the user and can be easily hit, it's similar to bug 347633 in that it's also a mouse clicking usability bug, so the usability keyword could be added too.

Also the product of this bug could be changed to "View as Icon" as the List view does not have this bug.
Comment 2 David Prieto 2006-08-02 12:13:11 UTC
Do you guys thinkthis bug could be adressed anytime soon?
Comment 3 Nelson Benitez 2006-08-14 11:04:29 UTC
Bug 121111 could be somewhat related to the root of this bug.
Comment 4 Christian Kirbach 2006-11-11 02:05:42 UTC
*** Bug 373181 has been marked as a duplicate of this bug. ***
Comment 5 Christian Kirbach 2006-11-11 02:07:41 UTC
thanks Nelson
Comment 6 Nelson Benitez 2007-11-03 17:24:43 UTC
Created attachment 98463 [details] [review]
Patch for Bug 347423 – double-click doesn't open half-shown items

Hi, I've made a patch for this, the patch retards the reveal of the icon one second, so there's enough time for double clicking before the icon moves. This is what windows explorer does and seems the best solution.
Comment 7 Christian Neumair 2008-04-02 13:28:12 UTC
Rejecting patch, delaying icon revealing by a fixed amount of time is really a crude hack.

For instance, it will not fix the issue if the double-click delay is larger than the fixed time interval, and for people who want to reveal the icon, it will not reveal it immediately.

The proper fix is to modify the handle_icon_button_press() handler:

In the !details->icon_selected_on_button_down case, when calling select_one_unselect_others(), we would have to set a flag in the container that we revealed an icon.

When we later handle the double click, we can modify the

if (event->type == GDK_2BUTTON_PRESS)

check in the same function [handle_icon_button_press()] to also do


if (event->type == GDK_2BUTTON_PRESS ||
    (flag && clicked_within_double_click_interval()))

This check would have to work more or less like the "gtk-double-click-time" check in nautilus_icon_container_did_not_drag().
Comment 8 Nelson Benitez 2008-04-21 01:21:57 UTC
Created attachment 109605 [details] [review]
Patch implementing cneumair guide to fix this bug :)

Hi, this patch is working well for me, I also tested it under single-click-mode.
The patch follows Christian's precise indications, and it works much better than my crude hack! :)

Thanks Christian!
Comment 9 Nelson Benitez 2008-04-21 01:44:21 UTC
Oh,, and for bonus points, it seems my patch also fixes bug 430667 .. this is a lucky day!
Comment 10 Jared Moore 2008-06-03 03:40:41 UTC
When I try this patch it has some problems. When I double-click a directory in browser view, the directory is opened properly but the location bar is not updated, so when I press "Up" it goes up to the wrong directory.
Comment 11 Nelson Benitez 2008-06-20 13:01:12 UTC
Thanks for spotting this, I can see the bug, will try to fix it next week...

O(In reply to comment #10)
> When I try this patch it has some problems. When I double-click a directory in
> browser view, the directory is opened properly but the location bar is not
> updated, so when I press "Up" it goes up to the wrong directory.
> 

Comment 12 Nelson Benitez 2008-06-26 11:14:01 UTC
Created attachment 113455 [details] [review]
Updated patch

It's now fixed, the problem was that a gtk double click generates the following events:
GDK_BUTTON_PRESS
GDK_BUTTON_RELEASE
GDK_BUTTON_PRESS
GDK_2BUTTON_PRESS
GDK_BUTTON_RELEASE

so the icon was activated twice, one for the two button press that made it enter in the clicked_within_double_click_interval() part of the 'if clause' and one for the GDK_2BUTTON_PRESS part of the 'if clause'..

So I remove the GDK_2BUTTON_PRESS part of the 'if clause' because now it's redundant and now the icon is activated only once.

I've checked it works well both in browser,spatial and single-click-mode..
Comment 13 Christian Neumair 2008-06-28 11:42:11 UTC
Thanks for your efforts Nelson, that was indeed a typo in my instructions. Please commit the patch to trunk and to the GNOME 2.22 branch.

I will look into the issue described by Jared in comment 10, the first version of this patch probably triggered another bug introduced with the GIO migration I have not been able to hunt down for some time, namely that sometimes the back/forward navigation is "stuck".
Comment 14 Christian Neumair 2008-06-28 12:22:52 UTC
Just FYI, I just fixed the nasty bug in trunk and in the GNOME 2.22 branch, which was revealed due to double activation:

http://svn.gnome.org/viewvc/nautilus?view=revision&revision=14288
http://svn.gnome.org/viewvc/nautilus?view=revision&revision=14287

It turns out that we did not properly cancel the pending location change when the old view was re-used for the new location.
Comment 15 Nelson Benitez 2008-06-28 17:02:29 UTC
(In reply to comment #13)
> Thanks for your efforts Nelson, that was indeed a typo in my instructions.
> Please commit the patch to trunk and to the GNOME 2.22 branch.

Sorry, I don't have commit access, so please then commit them for me.