Re: Invalidating preview cache in Motion
Re: Invalidating preview cache in Motion
- Subject: Re: Invalidating preview cache in Motion
- From: Darrin Cardani <email@hidden>
- Date: Fri, 13 Mar 2009 09:27:29 -0700
On Mar 13, 2009, at 5:45 AM, Eberhard Ammelt wrote:
we have a problem with custom parameters in Motion (3.0.2).
After creating a RAM preview in Motion (3.0.2), Motion ignores value
changes of custom parameters, and does not invalidate the preview
cache.
I've tried a workaround with changing hidden and visible standard
parameters programmatically, but it doesn't help.
Is there any way to force Motion to re-render and invalidate the
preview cache upon changes of custom parameter values?
Nasty. Sounds like a bug. Please file a bug report if you haven't
already. I know we've had a few bugs in the past regarding custom
parameters and updating, so it's possible we still have a few more we
didn't know about. My workaround would have been to try what you've
already tried with an invisible parameter. I don't have any other
ideas off the top of my head. (OK, if you wanted to try something
really nasty that's extremely likely to break in the future, or even
in different language versions, you could try convincing Motion to
clear the Ram Preview cache by faking a menu event, or something like
that. But I don't recommend it.)
Darrin
--
Darrin Cardani
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