Perspective - Custom property and view parameter schema support
planned
T
Tim Johnson
It would be great to either:
a) Assign a parameter type (color picker, path picker, icon picker, etc) to a particular parameter meta data, or
b) Have the parameter type inherited by binding, so that if a parameter is bound to a color property, it automatically provides the color picker, etc.
Log In
P
Paul Griffith
Merged in a post:
Allow Dropdown type of Perspective View Parameter
C
Charles Ahrens
A dropdown parameter could have a set list of values that are acceptable, instead of relying on the user to remember the specific syntax of what parameters are allowed, similar to the built-in components. For example, comparing a built-in symbol to a custom made embedded view shown below, the user has to type in "p&id" for appearance instead of picking from a dropdown, and the designer of that view has to either communicate that only "p&id" is acceptable, or build in error catching for "pid", "PID", and "P&ID".
P
Paul Griffith
Merged in a post:
Custom Props Properties
A
Alex Marks
Add more properties when adding custom props. Allow type to be explicit, and add a "description" field that pops up when hovering over the custom property/parameter.
R
Ryan Perretta
Just thought of this enhancement when adding a couple of new session properties and a couple others asking me how they are supposed to be used. Would really love to see this feature, as semantic naming seems to only help to an extent. It would save a lot of back and forth for picking up from where someone else left off on a task as well.
Ideally, if a 'tooltip' option would show up as an item in the context menu that appears when right clicking a custom property and allow us to enter a tooltip that would show up just as the base component properties have:
P
Paul Griffith
Merged in a post:
Custom properties and parameters validation
S
Steven Cheron
Add the possibilty to create a validation on a custom property or on a parameters with dropdown, possible types (one or more type) or regular expression.
For example, on valve template, the possibility to have a parameters to turn the valve template (top, right, bottom, left) with a dropdown.
Or for tagpath parameter, the possibility to define that can only be a string with some "/" and "[ ]".
P
Paul Griffith
planned
We have a feature in the backlog to allow defining your own schema for view parameters, such that you could do all the things we can do in
props
- define enums, define ‘suggestions’, define tooltips, etc. This would include specifying a "type" for properties, which would tell the JsonEditor to bring up the appropriate helper.