Re: saving plugin internal state
Re: saving plugin internal state
- Subject: Re: saving plugin internal state
- From: Paul Schneider <email@hidden>
- Date: Mon, 17 Aug 2009 11:45:08 -0500
Hi Brian,
the only "plugin state" that gets saved with the project is parameter
data. As Steve says, you can use a hidden custom parameter to
implement per-instance plugin state.
There's no way to specify per-sequence or per-project state. Keep in
mind that an FCP project can contain multiple sequences, and you can
also have multiple projects open at once in FCP. I'm not sure how you
could maintain a per-sequence or per-project singleton even in memory
(since you don't know what project or sequence you're in), let alone
save it with the project.
- Paul
On Aug 8, 2009, at 6: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?
-- Brian
_______________________________________________
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