You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In writing FxPlug frameworks, keeping track of the type for dynamic parameters is an outrageous complex engineering task that would be simplified with this one simple call. We may not know what a parameter's type is as a framework developer.
Exposing this property of parameters is absolutely critical.
Describe alternatives you've considered
putting an abstraction layer on the related protocol to trap the Parameter Creation and deletion methods to keep track of parameter types in a Custom hidden non-animatable inaccessible parameter that holds an array of parameters and their related types. Keeping track of this information is a headache.
Apple Feedback Assistant ID: MISSING!
Is your feature request related to a problem? Please describe.
In writing FxPlug frameworks, keeping track of the type for dynamic parameters is an outrageous complex engineering task that would be simplified with this one simple call. We may not know what a parameter's type is as a framework developer.
Exposing this property of parameters is absolutely critical.
Describe the solution you'd like
Please add
to FxDynamicParameterAPI_v4.
Describe alternatives you've considered
putting an abstraction layer on the related protocol to trap the Parameter Creation and deletion methods to keep track of parameter types in a Custom hidden non-animatable inaccessible parameter that holds an array of parameters and their related types. Keeping track of this information is a headache.
Additional context
We would also need something like this:
I suspect the type is already internal, and just needs to be exposed. It'd be nice to have the FxParameterId as being its own type.
The text was updated successfully, but these errors were encountered: