Using Directory Opus Pro 10.2.0.1 (4683) x64
OS 6.1 (B:7601 P:2 T:1) SP 1.0 "Service Pack 1"
Hi there,
I am experiencing some unexpected behaviour with the new linked tab system.
The situation is this:
On the left pane of a lister I have a tab open to C:\dir1, on the right a tab to C:\dir2. The tabs are linked and slaved to each other. Traversing the subdirs of dir1 on the left tab will make the right tab follow the subdirs in dir2, as expected.
Now if I open another tab in the left pane and switch to it, and then switch back to the first tab that is c:\dir1, I notice that the right tab has been switched to c:\dir1 as well. I would expect activation of a tab to not change the current directory of a linked tab.
Is this a bug or am I simply misunderstanding the linking system?
Expected or not - it certainly sounds undesirable... good catch. Haven't messed with slaving the linked tabs myself yet - mainly because of how this behavior (when "expected") results in the same sort of undesirable messing about with the un-synced folder as Navlock in v10 does... much to extreme chagrin . I actually chuckled at the description of how the slave tabs differ from Navlock in this respect because exactly the same thing happens in some cases with Navlock as well when you get in and out of sync.
That doesn't seem to happen for me, unless I click on the linked tab again once it is already active.
@Steje: I don't think anyone on our side ever understood what you meant by the NavLock going out of sync in Opus 10. Maybe a video would make things clear as trying to describe it in words never got us anywhere. (In another thread, of course.)
Funny, now I cannot reproduce this, except for what Leo said. In any case I would say that this behaviour is still undesirable.
An added twist: If I make the linked tabs both "Locked (Allow folder changes)", when the left tab is not in it's "home" dir, and is switched out for another (so when leaving the tab), the left tab goes back to the home dir and the right tab will change to the homedir of the left tab.
Maybe if both tabs are locked, when the master returns to its home directory the slave should go back to its own home dir rather than that of the master?
To add two cents to the discussion...
I wonder if going forward some confusion may arise from slave tabs having some element of "pure slave" (show the same absolute path as the other folder) and some element of "navlock" (show the same relative path as the other folder).
This is bound to invite people to use slave tabs when they really want linked navlock tabs, with some unexpected consequences.
My own hunch would be to clear this up by splitting the Link Tabs options into three types of links:
Plain Link (you click on a tab, the other tab becomes active)
Slave Link (you click on a tab, the other tab becomes active AND follows the other tab's absolute path)
Navlock Link (you click on a tab, the other tab becomes active AND follows the other tab's relative path)
. I actually chuckled at the description of how the slave tabs differ from Navlock in this respect because exactly the same thing happens in some cases with Navlock as well when you get in and out of sync.