Re: Fields vs. frames, and parameter saving
Re: Fields vs. frames, and parameter saving
- Subject: Re: Fields vs. frames, and parameter saving
- From: "Hugh Denman" <email@hidden>
- Date: Mon, 15 Oct 2007 00:29:26 +0100
Just to wrap up the discussion on parameter saving - it seemed in the end that a custom parameter specified with kFxParameterFlag_HIDDEN would not be reloaded by FCP. It works when I specify the CUSTOM_UI flag, but only if I also supply a valid view in createViewForParam for the parameter in question.
Also, I found that my parameterChanged method was being invoked as the project was loaded from the disk, before a render had occured. I react to a parameterChange by invalidating the stored analysis data in the customParam, so I was clearing it before my first render. I got around this by adding a 'firstRenderDone' flag, intially false but set to true in renderOutput, and ignoring 'parameterChanged' messages while this flag is false.
Hugh
--
email@hidden+353876290136
_______________________________________________
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