As one of Vuo's developers, I work on Vuo's engine (the thing that makes compositions run), work on nodes, and write documentation. You'll see me on the forums answering people's questions about Vuo.
I enjoy using Vuo to make live music visuals. My hope for Vuo is that it will grow into a community of people of diverse backgrounds and identities making lots of different artistic, useful, unique, goofy, beautiful, crafty, wonderful compositions.
Estoy practicando para ser competente en español. Si publicas en el foro en español, trataré de responder en la misma manera.
We have implemented the "global" and "local" levels.
If a subcomposition is installed in ~/Library/Application Support/Vuo/Modules or /Library/Application Support/Vuo/Modules, then all compositions can use the subcomposition and all compositions see any changes to it. — same behavior as now
If a subcomposition is placed in a Modules folder next to a composition, then only that composition can see the subcomposition. Other versions of the subcomposition can be placed in Modules folders elsewhere in the filesystem and are not affected by the changes to the first one. — new behavior
Alastair (@usefuldesign), I want to bring this discussion back in a constructive direction. I understand you're frustrated and I agree that Build List and Process List can be tricky to get working for non-trivial situations. A lot of people have had the similar questions. If you look for past discussions on Build List and Process List, you'll see several times where someone shared their composition and asked how to get it working, and with the community's help they were able to. These nodes are admittedly not the easiest to use, but they do get the job done if you're willing to have the patience, and they're hopefully better than nothing. Please bear with us until we're able to implement a more robust method of iteration.
While I and the rest of Team Vuo welcome suggestions on how to improve Vuo, or even measured comments on what you found difficult to learn, your recent comment comes across to me more as venting. I really am sorry that Vuo is falling short here. But that kind of comment is just not constructive or helpful toward solving the problem.
I think you're on the right track to be using Display Console Window in your debugging attempts. Without seeing the composition, I'm not sure why it's not working as you expect. Maybe if you post your composition someone can help.