site_archiver@lists.apple.com Delivered-To: Pro-apps-dev@lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=S9GYwFS7r8o/FGJ37+eH+aPPkf/F+mMzRlHd5ofkaM8TfHwGvHTt5o2HQVIDMJYG; h=Received:From:To:In-Reply-To:Subject:References:Message-Id:Content-Type:Content-Transfer-Encoding:Mime-Version:Date:Cc:X-Mailer:X-ELNK-Trace:X-Originating-IP; Thanks, Darrin. Yes. No problem with that case. You are correct up to this stage. There is no issue until the user decides to alter a global value by changing a parameter value. Unfortunately, I can't figure out how to do that. So, the best I can do is using a singleton ... which is probably Project scoped, which is acceptable. -- Brian _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... I think recovering the state should be fairly easy. In the case where "useGlobalValues" is not checked, you don't need to even create the singleton, so that case should work just fine already, right? This shouldn't be a problem in practice. When you first create the singleton, it has the values of whichever instance of the plugin asked for it to be created. The next plugin calls the create method, but just gets back the existing instance, so it has the same values and is in synch already. All instances that exist when the document is saved should already be in synch. So when the document is reopened, they'll still be in synch. That parameter change will in turn update the corresponding global value, stored in the singleton. At this point, all of the other plugin instances set to useGlobalValues will have a parameter value that still is set to the old global value, except the one that the user has just changed. So, the change must be rippled to all of the other instances of the plugin. Normally, I'd expect to do this by having the singleton maintain an array to keep track of the relevant plugin instance id's. Toggling an instance's useGlobalValues parameter, would add/remove it from the singleton's array. The singleton could loop through this array, to send a message to each managed plugin instance to perform a setParameter, to reflect whenever a global value changed. But... just after an 'open project', the id's are not the same as in the previous session (I think), and the singleton has an empty array anyway (singleton data wasn't seralized). So, this array would need to be reconstructed somehow after the 'project open'. Since the deserialization of the useGlobalValues parameter bypasses ParameterChanged, it never invokes the singleton. So the singleton can't build a list of the relevant plugin instance's new id's. Perhaps, I can replace the toggle with a 'custom parameter' toggle, just so that i can trap the deserialization? Then I could (re)build a new array upon project open. You can also use the operating system mechanism for saving preferences. See NSUserDefaults for the details. ... ... It also means all instance of your filter, regardless of project, use the same global settings. I don't know if that's what you need or not. Definitely would be an issue -- not what the user wants in this particular case. Actually, the user wants these globals to be scoped to the sequence. Almost like a Sequence Setting (but with easier access, since the globals are changed more often). Though, if the user can open multiple projects in one session, then it's probably not even project scoped, it's probably session scoped. (Session scoped is also not very desirable, either.) Certainly, somehow, these global settings must be scoped and stored within the Project file. This email sent to site_archiver@lists.apple.com