New mode of behaviour of locked tabs

[piotr.dobrogost]

Hi

I love locking feature available for tabs but I very much miss the feature of being able to change directory of a locked tab as long as I stay underneath the original directory in the directory structure.

Do you also miss this feature?
Are there any plans to add this to TC?


Regards
Piotr Dobrogost

[MVV]

You may set tab's option 'locked but directory change allowed' - in this case TC will allow to change dir in this tab but will revert dir back to locked after restarting/switching tab/pressing Ctrl+\ etc.

[piotr.dobrogost]

Thanks for your replay.
I've seen this option but it does not force you to stay underneath the original directory. Nevertheless this is the solution I'm using now. Thanks again

[JohnFredC]

I requested this exact thing a long time ago. Sort of a "virtual root" for the tab. Incredibly useful, and available in one particular TC competitor.

Just one of several improvements to tabs in TC that are long overdue.

So long overdue, in fact, I've given up.

[ghisler(Author)]

What would be the advantage of forbidding the user to go up from the locked root? I don't see any, just one more restriction. Please explain.

[piotr.dobrogost]

What would be the advantage of forbidding the user to go up from the locked root? I don't see any, just one more restriction. Please explain.

Why to lock a tab at all one could ask. It's just one more restriction too Voluntary restrictions are good They can be thought of as yet another way to organize one's workspace.
A subtree in a file hierarchy is the most common way of grouping files which belong to some project. Taking this into account it's convenient to restrict some tab to given subtree. Leaving such a subtree staying at the same time on "its" tab has no sense and thus if tried should be treated like a will to open a new tab instead.
As an example I have a programming project which, among others, has a folder named "modules" with source files. This folder has a subfolder named "base" with source files of base classes only. I would like to have a tab locked to "modules" subtree so that I could navigate between "modules" and "base" folders back and forth. At the same time I don't want to be able to go above "modules" folder because this tab is meant for modules only. For other types of files I have other tabs.

I hope this makes it clear why this feature would be helpful.

[JohnFredC]

What would be the advantage of forbidding the user to go up from the locked root? I don't see any, just one more restriction. Please explain.

Naturally, that would be an "optional" restriction. All behaviors and configurations should be optional.

I keep hoping for a tab property panel similar to this example. If you'll step back a bit (and not be put off by the size of the dialog or its layout or possible irrelevance to your specific method of working) you may see how much more enabling such an approach to tab configuration and behavior could be for some of us. Look at each setting carefully before you dismiss it. (The issue mentioned at the top of this post is addressed in the "navigation" section of the dialog.)

As a person who has made my entire living writing software for other people to use in my absence, I have found it important always to keep in mind that not all of us have the same work habits and that methods which work best for one task are not always the best for another task. TC folder tabs are great. But they could be a lot better and I am sure my suggestions (as shown in the link above) only scratch the surface of what the user population at large would find useful.