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.
I'm writing a FCP plugin in FxPlug and it needs to know if the user published a parameter in Motion.
Describe the solution you'd like
FxParameterFlags should have a flag for if a parameter is set to be published in Motion or published in FCP. Operationally, consider maybe read/write in Motion and read only in FCP. This maintains the Motion effect user's desire to not publish a parameter. Dynamically created parameters in FCP are published by default and thus have the flag turned on.
If an unpublished parameter is linked to a published rig, this flag is OFF because the parameter is not published. This could probably be presumed, but I want the requirement to be clear.
Describe alternatives you've considered
No other way.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Apple Feedback Assistant ID: MISSING!
Is your feature request related to a problem? Please describe.
I'm writing a FCP plugin in FxPlug and it needs to know if the user published a parameter in Motion.
Describe the solution you'd like
FxParameterFlags should have a flag for if a parameter is set to be published in Motion or published in FCP. Operationally, consider maybe read/write in Motion and read only in FCP. This maintains the Motion effect user's desire to not publish a parameter. Dynamically created parameters in FCP are published by default and thus have the flag turned on.
If an unpublished parameter is linked to a published rig, this flag is OFF because the parameter is not published. This could probably be presumed, but I want the requirement to be clear.
Describe alternatives you've considered
No other way.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: