Yes it will be triggered on every item, and the output list Finished Building once it's done.
For the other output ports I don't remember if they only output once done, but as Jaymie from the Vuo Team pointed out to me, there is a little bug with this custom node that produce extra events in the loop.
Is there a particular reason you wanted to use this custom node as opposed to the built-in stock Build List node ?
Maybe if you explain what you want to achieve it's surely possible using the stock node and some Hold nodes.
so I'd like to see this feature request get up too. I have one solid idea I've been sitting on for years and even with all the streaming software and BlackMagicDesign mini ATEM revolution this concept I started in QC as a custom layer for mimioLive still has unique features in the market.
i would certainly be prepared to pay the US$99 p.a. if i had a Vuo authored app that was viable for the macOS App store (and eventually iOS maybe given Apple Silicon convergence around ARM and iOS) . ditto for paying team Vuo to walk me through the code signing.
strangely I have one free apple developer account that gives me full access to code bug submissions and FRs etc and another free Apple deve account that only gives me limited access to Apples developer tools, videos and programs. By rights both should lock me out of the developer forums, but one is able to post. Go figure.
workaround feature request: local sub-compositons ;-)
in QC the way around this was to throw a patch or group of patches inside a "Macro" (a box that looks like a single patch and if you double click you navigate down into it's composite patches). All the ports of Macros can be relabelled at any time, as could be a local sub-composition.
I'm not going to come back to Vuo until various forms of in editor accessible/navigable sub-compositions become a thing I think. I do have a erect in mind but I really think Vuo is too hard without this.
Problem: For many nodes, ports are labelled with numbers only. For nodes like Render Layers to Image, Render Layers to Window, these are currently labelled with numbers only. For others, there are no labels are all. The result that it's easy to forget which is which, without tracing the cables back through the composition. Real-time thumbnails may help, but will not help for numeric values, or when composition is not running.
Request: Right click on a port to rename, or add a name to a port. Easier version is to do this for ports that are currently labelled with numbers.
for example, these labels might be 'cow' 'moon' and 'starry background' for images. Or 'motion index' or 'mouse movement vector'. These are, in essence, variable names.
Bonus points: Allow labelling to cascade through an entire flow.
funwithstuff I think one way @teamVuo mentioned to me to make runtime compositions very broadly distributable is compile it Portable Native Client (PNaCl) which is being depreciated next year in June in deference to WebAssembly. There's also WebGL, which WebAssembly authoring tools can bind to. If you can compile for a web app, then Electron allows you to build a double click desktop application from that code base. Examples are the Slack and Visual Studio Code apps which use the open source Chromium engine under the hood to get native like performance. Not sure how it copes with higher demanding graphics… but several 1st person shooter games were ported to NaCl in the early days.
To me every decision Kosada makes around new features needs to answer one set of questions first… what is the unique power of Vuo and is there a market for it that can grow the income to get the tool to where we'd all like it to be, and keep the tool up to date with industry trends and emerging technologies.
If there isn't a ready market today, where is the closest market and how can Vuo be modified/ported to access that market. Incredible things happen when scale of a user base doubles every n months. Manifold changes in the community take place, from user contributions to the code base (which would mostly mean OSS compositions and new nodes in the case of Vuo) to word of mouth and buzz to periodic doubling of income for the maintainers of the code base or volunteer code contributions and maintainers (would mean doublings of Pro subscriptions in the case of Vuo).