cm_GoToRoot with Locked, but directory changes allowed

[Ged]

Not sure if this is a bug or intentional behavior.

I really like how "Locked, but directory changes allowed" works in TC9, but in beta 7 I just discovered what I think is unexpected behavior of cm_GoToRoot.

1. Lock a tab to "c:\foo" using "Locked, but directory changes allowed".
2. Then use that tab to go to "d:\bar"
3. Trigger cm_GoToRoot via hotkey or by pressing the [\] button.

Since I'm in "d:\bar" I would expect to be taken to "d:\". Instead I'm taken to "c:\foo".

[umbra]

Hi,
it is intentional and has been for quite some time.

If you add LockedGoToDriveRoot=1 to your wincmd.ini, cm_GoToRoot, '\' button and CTRL+\ will always take you to the root of the drive.

Then, you can either click on a locked tab header or use cm_GoToLockedDir to go to the locked path.

[Hacker]

[mod]Moved to the English forum.

Hacker (Moderator)[/mod]

[Ged]

Thanks.

I get the behavior I expected with LockedGoToDriveRoot=1.

I personally think this should be the default setting now that you can click on the tab to go back to the locked dir.

[Ged]

One more suggestion for new defaults. I think it makes sense for CTRL+Backspace to trigger cm_GoToLockedDir since backspace already triggers cm_GoToParent and there are already two default hotkeys for cm_GoToRoot (at least on my keyboard).

Both suggestions for new defaults:

Code: Select all

[Configuration]
LockedGoToDriveRoot=1

[Shortcuts]
C+BACK=cm_GoToLockedDir

PS. If a mod wants to move this thread again, to the suggestions forum this time, feel free.