Let’s use an example to describe the expected behaviors:
- In the “Shared” Page Configurations, let’s say we have a north-oriented Docked View which uses a View named “StaticTop” which is set to “visible”. This Docked View will be used for EVERY Page I configure within the project, and since it is set to “visible” it should be visible immediately.
- I also have an individual Page Configuration for a page (
/demo) where I don’t want “StaticTop” to be used for some reason. I configure a different north-oriented Docked View: “OneOff” which I also set to be “visible” because I always want it to be seen.
Using this example, when I navigate to /demo in a Perspective Session I’ll actually see StaticTop because we have two Docked Views set to be visible, and StaticTop was assigned first.
There are two ways to resolve this:
Correct way:
In the /demo Page Configuration, make an additional Docked View with a North orientation which uses the “StaticTop” View, but set this Docked View’s “display” setting to “onDemand” and set the “handle” property to “hidden”. Leave the OneOff Docked View as you’d like it.
Alternate Route:
As part of the View onStartup for the View which you do not want the StaticTop Docked View displayed, you can include a scripting call to close the StaticTop Docked View.
There are a couple fo reasons this method is not recommended:
- You might use this View on other Pages, where it would also close the StaticTop Docked View. You should never put anything in a View onStartup script which you don’t want to happen every time a View is opened.
- You have a hard-coded id in the closeDock function call, so if the Docked View’s id ever changes you have to go and find this script and update it.