| Micah, To answer your question, no, it doesn't reset correctly for me either. I'll file a bug about this. In the meantime, I'm not sure what sort of workaround you could implement. One option that I haven't actually tried would be to modify your -parameterChanged: method to see if all the other parameter values are set to their defaults and if so, modify your custom parameter to its default. (You'd have to check that the parameter being changed wasn't the custom parameter before doing that, otherwise it would continuously get reset as the user changed it.) That seems fraught with error, though. For example, if the user changed the custom parameter, then was changing a regular parameter and happened to pass by the default value, you might accidentally reset the custom parameter. I don't know that there's any good way you can work around this.
Darrin On Jan 29, 2008, at 11:01 AM, Micah Sharp wrote: That is weird. I see encodeWithCoder then initWithCoder then encodeWithCoder twice.
I apply SimpleMatte, make a quick matte, then go put a break point at the two methods, and hit the reset button in the Inspector Filter tab. I have 3.0.2 as well. Either way, it doesn't reset. Does it reset the matte correctly for you?
Should I do a screen capture of it breaking? Thanks,
<Picture 3.png> On Jan 29, 2008, at 10:24 AM, Darrin Cardani wrote:
On Jan 28, 2008, at 5:04 PM, Micah Sharp wrote: Hi guys, we are noticing our plugins that use custom data/controls are resetting correctly when hitting reset in FCP, but not in Motion. The only difference I can see is that in FCP only encodeWithCoder is called upon hitting the reset button, where in Motion both encodeWithCoder and initWithCoder are called. The SimpleMatte example shows the problem perfectly.
It seems to work for all other controls without any problems. Any hints about how to make it work are appreciated.
Micah, I'm seeing something different than you. In Motion 3.0.2, when I click on the reset button in the Filters tab in the Inspector window, Simple Matte's -encodeWithCoder gets called twice. I'm not seeing -initWithCoder getting called again. Can you describe the steps you're going through to reset the filter?
|