Multi Commander > Support and Feedback
Locked TAB functionality.
GrantSP:
--- Quote from: Mathias (Author) on March 27, 2014, 09:49:10 ---Settings if it should open new tab when going to new location of tab is locked is already added in the current beta
--- End quote ---
Somehow I think you are misunderstanding the point of this topic. :(
Regardless of whether I have the option checked or not, whenever I move UP the path a new Tab is opened.
"Lock Tab - Allow subpath change" is great, I use this ALL the time on my locked tabs. It keeps my locked Tab and all the sub-folders together.
That option is not in question. It does what you intended and what I need. It is the moving UP the path that is broken.
Sometimes when I click, " .. ", to move up the path, I sometimes click again by mistake and a new Tab opens with the parent folder.
It shouldn't! That is the aspect of 'Locking the Tab' that should be addressed.
A simple error message or audible error tone or something, just to alert the user, "Sorry, you don't want to go that way, you have locked the Tab."
Likewise clicking the higher level folders in the pathname shouldn't be possible when this option is chosen.
C:\TopLevel\SecondLevel\ThirdLevel\FourthLevel\FirstChildLevel\Folder1\Folder1a\Folder1b\
In this example the locked Tab is FourthLevel. All the folders under this should, and do, open in the same Tab.
Anything above that, C:, TopLevel, SecondLevel or ThirdLevel should return an error message of some kind indicating access from this 'Locked Tab' is denied.
Otherwise the functionality of 'locking the Tab' is gone. I can move freely up and down this directory tree without locking tabs, all locking them does is start a new Tab. If I wanted a new Tab I can simply Ctrl-T and make one using the current folder as a starting point.
Mathias (Author):
--- Quote from: GrantSP on March 30, 2014, 04:06:27 ---
--- Quote from: Mathias (Author) on March 27, 2014, 09:49:10 ---Settings if it should open new tab when going to new location of tab is locked is already added in the current beta
--- End quote ---
Somehow I think you are misunderstanding the point of this topic. :(
Regardless of whether I have the option checked or not, whenever I move UP the path a new Tab is opened.
"Lock Tab - Allow subpath change" is great, I use this ALL the time on my locked tabs. It keeps my locked Tab and all the sub-folders together.
That option is not in question. It does what you intended and what I need. It is the moving UP the path that is broken.
Sometimes when I click, " .. ", to move up the path, I sometimes click again by mistake and a new Tab opens with the parent folder.
It shouldn't! That is the aspect of 'Locking the Tab' that should be addressed.
A simple error message or audible error tone or something, just to alert the user, "Sorry, you don't want to go that way, you have locked the Tab."
Likewise clicking the higher level folders in the pathname shouldn't be possible when this option is chosen.
C:\TopLevel\SecondLevel\ThirdLevel\FourthLevel\FirstChildLevel\Folder1\Folder1a\Folder1b\
In this example the locked Tab is FourthLevel. All the folders under this should, and do, open in the same Tab.
Anything above that, C:, TopLevel, SecondLevel or ThirdLevel should return an error message of some kind indicating access from this 'Locked Tab' is denied.
Otherwise the functionality of 'locking the Tab' is gone. I can move freely up and down this directory tree without locking tabs, all locking them does is start a new Tab. If I wanted a new Tab I can simply Ctrl-T and make one using the current folder as a starting point.
--- End quote ---
But.... That is what that new option do.
If you disable the settings "Open new tab when going to new location if tab is locked" in (Explorer Panel Settings under the Tab category)
If I go to C:\MyFolder\Folder1 then I lock the tab. Then if I tries got to ".." or click on C:\MyFolder or something else that would take me way.
It would not allow that and a new tab with that path is NOT create. No new tab and current tab is still at the same path.
fortuinw:
Awesome Mathias! That option works perfectly for me! Thanks so much
GrantSP:
Mathias, I am sorry, I kept checking for an update using "Help" -- "Check for updates" but nothing showed as being available.
It was only when I ran the MultiUpdate tool that a new update was provided.
Yes, as you say, there is now that option in the settings. And it works PERFECTLY!!
Just want I wanted. Thank you.
So can I conclude from this that the setting inside the MultiUpdate tool to also include 'beta' updates doesn't apply in the menu command?
Mathias (Author):
--- Quote from: GrantSP on April 01, 2014, 02:53:26 ---Mathias, I am sorry, I kept checking for an update using "Help" -- "Check for updates" but nothing showed as being available.
It was only when I ran the MultiUpdate tool that a new update was provided.
Yes, as you say, there is now that option in the settings. And it works PERFECTLY!!
Just want I wanted. Thank you.
So can I conclude from this that the setting inside the MultiUpdate tool to also include 'beta' updates doesn't apply in the menu command?
--- End quote ---
Under core settings you need to enable so that it checks and download Beta version, Then you don't need to run multiupdate separately
Navigation
[0] Message Index
[*] Previous page
Go to full version