This might seem like a minor issue, and it's never something you would run into unintentionally, but it's a bad practice/"design trick" we've noticed others doing in some projects. Using bindings like this can make Perspective issues difficult to trace/replicate and compound with other bad design practices to allow for some truly unexpected behavior.
The steps to replicate are:
-
Create a parameter on your view (testParam on a brand-new page in this case)
(I'm only allowed 3 images per post)
-
Change the directionality of the binding to either 'Output' (right arrow) or 'Input/Output' (bidirectional arrow)
(I'm only allowed 3 images per post)
-
Put a binding on the parameter (you are allowed to bind to Perspective params that have an output)
-
Change the directionality of the binding back to Input only (left arrow)
-
You now have a Perspective parameter with an illegal binding/state
(The expected warning is "Cannot configure bindings on input parameters," as referenced by testParam2, which was not intentionally tricked)
I'm not sure what the fix for this would be. Disable/gray out bindings on Input params? Delete the binding entirely? Throw a similar warning popup as above and not let the user change it back to Input only?