Hello,
I'm trying to edit parameters for a docked view in the page configuration window, but the view parameters window is so absurdly tiny. Is there a way to expand the viewing port? Or could this be added in a future update?
Thanks
Hello,
I'm trying to edit parameters for a docked view in the page configuration window, but the view parameters window is so absurdly tiny. Is there a way to expand the viewing port? Or could this be added in a future update?
Thanks
We have an internal ticket already in place to overhaul the entire Docked View configuration panel.
Curious how people like to use docked views in Perspective.
In our initial projects, I used docked views for a menu and header. But the Building Management System Demo (source available in the Exchange) was a complete shift in how I saw the potential uses of docked views.
There are so many practical applications for Docked Views... Below are just a few examples of ways we use them in some of our internal QA projects.
Static:
Headers/Footers
Navigation
User status
On-demand:
Alarm status
In-depth display of a selected item in a main view
Configuration of what is displayed in the main view (settings panel)
I also have developed some projects which use Docked Views (left/right) as a chat window between sessions.
I'm not sure where this ticket is upto, but I would love to be able to bind tags to parameters through the Docked View config panel.
I have the idea of creating a navigation tree of the entire site and all it's views/areas, and then a corresponding alarm symbol for each view/area that would be mapped to a tag. The alarm symbol would display to show in which areas there is a major fault in the plant.
Currently I can't think of a simple way to do this without being able to use tag binding.
Why can you not bind the tags desired to the dock view's custom properties?
Agreed. There's nothing stopping the View from using a Tag Binding. The relevant ticket is UI-oriented, and geared toward making the panel make better use of the available space.
Because the docked view will exist in an inherited project, that will be locked from modifications once it is used in a project. To make it useful for multiple child projects requires the tag bindings to be different per project, therefore I cannot use the view custom properties unfortunately
Ah, I see. You should start a feature request at the ideas site. I think adding the ability to set constants in page configuration for docked views makes sense. (A tagpath constant to drive that tag binding, in your case.)
I think the View in use for the docked view each project should override the parent and provide project-level information - like the project-specific tag path.
Can you only override part of a view? Overriding the whole thing breaks the maintainance of the view in the inheritable project. Yes, you could use an embedded view to wrap the inheritable dock, but that's pretty heavy (and has performance implications).
No.
As an alternative, you could have the View reference a Session property, or you could define the map of project -> Tag paths within the parent project.
Ah, didn't think of that. It's probably the best choice.