Pass parameter to docked view

Ignition
4

Indeed they would be. The handles (like in your screenshot) do nothing but expand/collapse the Docked View; there is no way to attach any logic, properties, or params to them.

There are LOTS of different avenues for moving data around in Perspective, and no one way is best in all situations. I'll cover some of the methods for Docked Views.

Params:
Pros:

  • Allow for initial-state setup of the Docked View

Cons:

  • Only dynamically writable in Actions (Dock, Script)
  • Page Configuration GUI only allows for "default" value.

Session Properties:
Pros:

  • Available at any point of the Session lifecycle
  • Completely Dynamic

Cons:

  • Large quantities of session properties can become unwieldy
  • These retain values throughout the Session, so overwriting their value in one spot could result in undesirable consequences depending on use.

Message Handling:
Pros:

  • No hard-coded paths
  • Easily reused between Views

Cons:

  • Splits code into two places (broadcast code, logic code)
  • Listeners not in browser DOM don't hear sent messages
  • No registry, so logging is best method of troubleshooting

So I would try to determine how the Docked View is going to be used:

  1. If the Docked View is going to be expanded (Display == visible) by default, you would need to use Params or Session Properties, as message handling requires a manual action of sorts.
  2. If the Docked View is based off of PAGE parameters, you could conceivably use a View Startup script for the page's primary View to invoke the openDock() script; in this way you can open both the "Page" and Docked View with parameterized values on initialization (of course, this will happen any time the View starts up).
  3. If you can reasonably provide a button - and the Docked View isn't expected to be expanded by default - then message handling is probably the way to go.

TLDR;
Given your specific use-case (parameterized dock is collapsed, user expands Dock manually), I would recommend NOT using parameters for the Docked View. Session properties might be best: perhaps session.custom.ply? Then instead of binding against DockedViewName.params.ply, you would bind against session.custom.ply.

2 Likes