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 642178 - Locked tab is not really locked
Locked tab is not really locked
Status: RESOLVED FIXED
Product: gnome-commander
Classification: Other
Component: application
2.0.x
Other Linux
: Normal enhancement
: 1.2.9
Assigned To: epiotr
epiotr
Depends on:
Blocks:
 
 
Reported: 2011-02-12 16:19 UTC by nm
Modified: 2011-02-20 15:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description nm 2011-02-12 16:19:55 UTC 
The new locked tab is not really locked in git release.

To verify this do the following:

1. Lock a tab on /home/[username]
2. Go one step back in that tab.

Result:
You go back. (Tab is not locked)

Trying to enter into /home/[username] however creates a new tab.

The only time the tab is locked is during startup.

Expected result (Well result that I would expect):
Going back enters a new tab which is going back. The other locked tab is still in place.

Now I am not sure which would be the best result but I see the following scenario as the tab not being locked. Any ideas?
Comment 1 epiotr 2011-02-14 20:53:47 UTC 
This problem has been fixed in our software repository. The fix will go into the next, 1.4 release. Thank you for your bug report.
Comment 2 nm 2011-02-15 23:30:10 UTC 
Thanks for the commit however I can still reproduce the problem.

The only time this does not occur is when clicking on .. in the window.

Backspace still makes the locked tab not stay locked.
Comment 3 epiotr 2011-02-20 15:30:48 UTC 
I see it now. The previous commit started a new tab when pressing ALT+LEFT/RIGHT keys (or clicking on FIRST/PREV/NEXT/LAST toolbar buttons).

I've fixed the problem - pressing LEFT/BACKSPACE will now  open a new tab for locked ones.
Comment 4 nm 2011-02-20 15:44:03 UTC 
Confirmed works now.

Thank you.