So lets make sure im right on this right - when an object is inside an iterator there is only one instance of it. The iterator then just reuses this object each iteration causing the resulting behavior.
Correct -- there is one instance, and one object executed multiple times. For stateless things (sphere, cube, filters sans accumulators, etc) this is perfectly predictable and what you want. for stateful things (some JS, smooth, CI Accumulators, and others) it's not what you want.
The reason I tried the smooth patch was because I'm writing my own plugin that averages data over a period of time and was having the same issue with it. How can I enable this plugin to know its inside an iterator and to not spaz out.
Using the official api, the only way to know if you're in an iterator or not is to add 2 additional inputs: current iteration, and total iterations, and expect the user to attach these appropriately to the iterator variables patch.
-- [ christopher wright ] [EMAIL PROTECTED] http://kineme.net/
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
