I've got a docked tab strip component that does the majority of the navigation for a project.
However, I also need to add contextual navigation buttons to take the operator to different areas when they click on a specific part of the screen.
How do I keep the docked view tab strip in sync with the windows as they swap from the contextual buttons? Or, is there another way that I have to do this with the button, to somehow "send the request" to the docked view?
Most people bind the tag strip to the current window system tag. As long as all of your main window operations use swapping instead of opening, it should stay in sync. (I can't remember when they went missing, but there were many Vision project templates available that showed how one would typically tie stuff together. Consider spinning up a v7.9 or v8.0 gateway to recover samples of those.)
So a bidirectional binding to the tab strip's Selected Tab property? Bound to what, exactly?
No, unidirectional. To the vision system tag that holds the current main window's path.
I'm just not seeing any system tags in the tag browser that would give me the current main window.
Had to rework a few things because this is actually a 2-tier system, but this was the solution.
Just not sure how to get the top level (tier 1) tab strip to switch when the context button directs to a screen that's under a different tier 1 tab.
What tripped me up, that's not immediately apparent, is the relationship between the Tab Strip and the Selected Tab property. I thought that the "button" part of the tab strip would cease to function if I bound this to the system's
currentWindow tag. In reality, all this property does is determine which tab should be highlighted by comparing it against the window name in the Tab Data dataset. That makes it much more obvious that this property should be bound to that system tag.