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=I5zo4Hz6SpNulH2twA8JxCsg3mhstW+a7rIfhIwUK5v/6YSM9sUJCczTx5VbChtR; 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; Good point, Steve. It does sound like arrays were a bad idea. I do like Darrin's suggestion of using NSNotifications. Seems more stable. I'll assume that NSNotifications doesn't have a similar issue, and will work properly even if the particular clip isn't currently being directly worked on. (Is that a valid assumption?) -- Brian steve _______________________________________________ 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... This makes the assumption that a plugin instance is created for each clip that uses your effect and that the instance will hang around in memory until either that clip is removed, the project is closed or the host app quits. I don't know the underlying architecture but it's just as likely that plugin instances are created as needed and then destroyed if you're not currently working with a particular clip. If you create an array and add instances to it, you -could- end up with a bunch of stale items that no longer refer to real clips and/ or conflict with the plugin instance that now manages your effect for a particular clip. ... This email sent to site_archiver@lists.apple.com