Re: updating custom parameter value does not force render (FCP)
Re: updating custom parameter value does not force render (FCP)
- Subject: Re: updating custom parameter value does not force render (FCP)
- From: Paul Schneider <email@hidden>
- Date: Tue, 28 Jun 2011 11:58:58 -0500
> Another CUSTOM anomaly. When I press RESET, my custom parameter is not getting it's value set back to the empty NSData that I used for the default value.
>
> Do CUSTOM parameters reset properly normally?
I just checked this with the SimpleMatte example in FCP 7, and it appears to work. You might not receive a -parameterChanged message during a reset, though.
On Jun 28, 2011, at 10:37 AM, Paul Miller wrote:
> On 6/27/2011 2:03 PM, Paul Miller wrote:
>> On 6/27/2011 1:48 PM, Paul Schneider wrote:
>>>
>>> Final Cut 7 won't re-render in response to changes in hidden
>>> parameters. One way to work around this is to change a visible
>>> parameter, even if the parameter data doesn't really have anything to
>>> do with the UI. For example, you could attach some data to your
>>> "Options" button parameter, and change that when you need to re-render.
>>
>> Okay I'll try that thanks!
>
> Okay this works.
>
> Another CUSTOM anomaly. When I press RESET, my custom parameter is not getting it's value set back to the empty NSData that I used for the default value.
>
> Do CUSTOM parameters reset properly normally?
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Pro-apps-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden