Re: saving plugin internal state
Re: saving plugin internal state
- Subject: Re: saving plugin internal state
- From: Steve Christensen <email@hidden>
- Date: Sat, 08 Aug 2009 17:56:08 -0700
If the state is something where you're using a snapshot of it at the
time your effect is applied, you can certainly go the custom, hidden
parameter route. Otherwise you might be able to embed something in
the project or sequence by sending FCP some XML via AppleEvent but I
haven't tried to do something that myself so it's just a guess. That
won't work as well if there are unsaved projects, though, since they
aren't terribly visible to the outside world (i.e., your plugin)
until they're saved at least once.
steve
On Aug 8, 2009, at 4:47 PM, Brian wrote:
Thanks for the tips, Steve.
Actually, I am trying to save the state of a singleton object.
(Neither per clip, nor global preference.)
So, it's more like a 'project setting' type of thing.
Or maybe even a 'sequence setting'.
I'd certainly love it to be a 'sequence setting'.
I'll definitely need to store the value inside the FCP (or Motion)
project file, somehow. Any ideas?
_______________________________________________
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