A large part of my work is writing about and sharing the Vuo story. We believe there are all kinds of people who will embrace Vuo once they discover it’s out there. So, my efforts include helping create the Vuo website, writing press releases, submitting conference proposals and generally figuring out how to create excitement and how to spread the word about Vuo. I occasionally help out with Vuo e-mail support and I'm part of the think-tank called "Team Vuo."
In Vuo 1.2.6 we added a menu item, "New Composition from Template." The three templates put several nodes on the canvas, including a Share Value node, labeled Time, which outputs events with the time at which the frame will be rendered, so that a constant stream of events can be used within a composition. Does that in any way help with this issue?
l know how frustrating it can be when you think something should work an it doesn't. We appreciate knowing that, and we'll look into whether we should create more examples, or how we can better clarify the documentation. We continue to work on more ways to do iteration in Vuo; we think Build List and Process List are two powerful tools for that.
In the node documentation for Build List, Built Item includes the sentence, "This port needs to receive each event fired by the Build Item port." We can be more explicit that this port should not receive any other (external) events, which could cause the node to behave erratically. You were right to put a Hold List in the composition. Instead of sending an external event via the Share List node to Get Item from List, the first Build Item event can send the list to Get Item from List. In general, when using values and lists within a Build List or Process List loop you want to make sure all the events to access or use those values or lists come from the Build Item port.
Again, I'm so sorry this was frustrating. Thanks for the insight. We will discuss how to make this more transparent.