It adds the input value to a running total, basically. So, in a
simple example, you could use it to have a boolean (a keypress, for
example) increment the X-position of a sprite. I think
mathematically, it's a bit more complicated than that, actually, as I
believe it takes into account frame-rate in some way, so the rate of
increment is constant for a given input value, irrespective of the
frame-rate of the composition. I'm hazy on the details though.
a|x
http://machinesdontcare.wordpress.com
On 9 Sep 2009, at 09:30, Keith Lang wrote:
Hi all,
I'm trying to wrap my head around the Integrator patch and what it's
doing mathematically, attempting to build a simple physics model
serving a few dozen objects.
Can anyone point me to a simple explanation of what the integrator
patch does, please?
Keith
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (Quartzcomposer-
[email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/the_voder%
40yahoo.co.uk
This email sent to [email protected]
_______________________________________________
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]
