The node set documentation for Transform (http://doc.vuo.org/1.2.6/node/vuo.transform/) has this statement:

"When the transformation is applied to a layer or object, the layer or object is first rotated, then scaled, then translated." Is that what you are looking for?

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.