first post, I'm just getting my head around vuo so forgive me if this is very obvious and my sample patch is wrong. I would appreciate all feedback :)
I'm trying to make a comp that will take a string of various lengths up to 144 characters, and then it will break it down so that it displays shorter messages bigger and longer messages smaller, for best readability while keeping the text all within a set area of my window. (red box in attached comp)
OK, Jaymie... the first XML was working the way I expected however I was using the output of the first XML as an input for searching the second XML and ran into a stange issue where it's returning an empty list. I can't figure out why... it looks right to me. I've gone over it about 30x and made changes to the naming I was using in the XML to simplify things and everything and I can't figure it out. Any ideas what I am missing? It's probably simple.
I'm really confused because after your suggestion above about using quotes I had no trouble getting the first XML to work and the second one is even more basic than the first.
I'm not sure what you mean with "regular" beside black hole Jaymie but from the question Push rendering optimisation I still could think something like "allow data to passthrough without modifying it" could be cool.
Perhaps the available options could be hardcoded in the nodes because for all nodes that have 1 single input / output that would still be cool. And as Jvolker stated "what state would those nodes be in when I restart the application" I assume compositions could save the state just like other ports, exported apps would need some kind of preferences plist or something ?
Why would the 3 states not be possible generally, but some nodes only have 1 or 2 of the 3 ?
But if a node had a bypass like "continue to flow the data without modifying it", would the node still have to process or will it not process and therefore spare hardware usage ?
Let's say that Vuo makes a tube and that the tube is scaled to 1x2x1. The tube outside material is an image that has already the good ratio for that scaled tube, so 1.57:1 rather than 3.14:1.
Is the image going to be applied to the tube before scaling (1x1x1 tube, so image stretched to 3.14:1) to be re-stretched after the tube scaling to 1x2x1? Or is the tube "constructed" first (with scaling) and than the image applied to it?
Are there any techniques to save me from processing nodes that are not resultant in the output, like a pull render system?
Imagine I have a generator like a noise image being driven by current frame, that then goes into some image filters individually like mirror, color effects etc. and I want to switch between each, ie just noise, noise with mirror, noise with color, with a "get items from list" .
If I do this, all of the nodes will be processing even though theyre not selected and their output is going nowhere.