Currently use QC to make custom layers for Bonix TV - a vision mixing kind of application for OS X with a kind of QC stack of layers, each layer being a composition with published ports and some protocols for data types. Also generate sports graphics and twitter feeds and so on for video score boards at large sporting venues.
Spent a few years learning Quartz Composer as my way back into coding from a decade away doing design related work. Film, graphics, studied Architecture for a few years and got involved in publishing then film. Now moving into front side web development. Hope to get into app dev with Vuo and rapid app prototyping.
Basically a composition to crossfade 2D point lists from List A to List B.
I'm continuously building a new list derived from the starting positions list and ending positions list using interpolation. A Curve node is used inside a loop ** Build List** node to transition from A to B for each point using the start point, end point and time input for the transition timing.
Thanks Xavierdev! When I wrote this I didn't know how to make a data wire into an event only wire (hold SHIFT key while dragging) so I couldn't run it into the Fire input port (why I put into the Refresh port of the Build List node). I ended up running the fire wire to the Refresh port of the Shared Value node before the Build List and that passed the event into the Fire of the Build List
Jaymie What is the point of the Refresh port next to the node title if it doesn't cause the node to execute? How can it be refreshing the output without firing? I see how it works for nodes will walls on the inputs (Shared List node for eg), it fires when you want it to rather than when the new data arrives. But in this case it doesn't seem to make Build List node fire.