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.
I think "chosen" for @teamvuo has typically implied chosen for the next release. Maybe a compromise is to make it chosen again after next major release :-) and hopefully it stays chosen until that release. Good idea, GeorgeToledo for an auto-firing 'performance mode'.
before add the refresh wire, the Hold node does output a list. The list never changes if I hover on the output port or tear it off as a floating window (as you'd expect because there is no refresh). But if I move the mouse away and bring it back the output list has updated, and change the order. Weird, but academic I guess as it's not being used correctly.
This is an overly complicated construct to shuffle a list of values btw, I got it working eventually in another comp but it's so frustrating handling loops/iteration in Vuo I think it needs some deep thinking. I hope the FR to have all nodes handle lists natively will help, but there's the cases where you want to do something unique, it's never straight forward like it is in so many text programming languages, and even QC is easier to loop lists etc for that matter IMHO.
I found that my use of the Measure Time node wasn't orthodox, I was pausing it once the timer went past the maximum value I was testing for and it had some strange side effects in terms of reseting and starting it. I removed the pause and it started working as desired.