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=re0oLUxtKgnhtuVJnmUtsIMs3/u+BcRJJa16KFWnC2wPoR/qm/yXHUmvbVQj+PVc; h=Message-ID:Date:From:Reply-To:To:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP; I am a little confused about the "variesOverTime" method. The default FxPlug template for a "filter" type FxPlug (which implements "brightness" by default), has the following code for "variesOverTime": - (BOOL)variesOverTime { return NO; } But doesn't the explanation comment above the code seems to indicate that this code is wrong? Since the two different frames will typically yield different results, even with the same parameter settings? (eg "brightness" stays = 1.0) So, frame 1 results can't be cached and reused for frame 2's results. The comment (and also API help doc) states: //--------------------------------------------------------- // variesOverTime // // This method should return YES if the plug-in's output can // vary over time even when all of its parameter values remain // constant. Returning NO means that a rendered frame can be // cached and reused for other frames with the same parameter // values. //--------------------------------------------------------- Could anyone clarify this for me? Is this a mistake in the documentation, or a mistake in the default code, or am I misunderstanding the docs? Thanks. -- 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... This email sent to site_archiver@lists.apple.com