Hey folks!
Just to set some context…
I’m a a relatively new user to Vuo Pro (thanks for the current discount pricing!). Know QC like the back of my hand, RIP . Have done a bunch of prototyping work in pretty much all the tools, including Framer, Origami, Principle.
I thought I’d selfishly make a list of a few little points of friction here.
Running a MBP, with old school Cinema display attached as primary display. Vuo 2.1.2. Catalina 10.15.6
Had a couple of crashes. Don’t remember seeing a crash report dialogue, but hopefully logs are going somewhere!
Vuo doesn’t seem to remember new document window properties, like other Mac apps? Ie, I want my window a certain size, etc.
When using Enter to insert a new Node from Node Library, it just wherever. Often on top of other nodes, or somewhere else I can’t find. Would love if
a. If another node is already selected, then place this node to the right of the selected node
b. If another node is already selected, do ^ and, if possible, connect up the new node. From memory, Facebook Origami does this.
The loading behaviour does a scale-to-fit on all nodes. Which I guess gives a sense of the composition, but in reality means I need to Zoom to 100% every. single. time.
I can scroll something like 200pt beyond any nodes on the canvas. I’d like to be able to scroll some more, so I can get a bit more space to work in, please!
The Preview window—I’d love if this would remember its position and Screen between launches/runs. I know I can wire up controls for that, but it seems like the default behaviour kinda six
I find debugging a little difficult. Ie double-clicking on node outputs to see what I’m dealing with.
a. Often lists/other data is truncated or flows in a way that’s hard for me to see
b. Sometimes I forget a composition is not running, so of course there’s no data. Would love a fix for that.
Save sheet seems to have the file extension (.vuo) still there. That’s not default behaviour on the Mac, would love for that to be hidden in the field.
I find the Push UI a little ungainly. Got myself in one scenario with a hair-pulling bug, but it was because one part of the composition didn’t get a push when it needed to. I don’t have a proposal at the moment, but could think up some ideas if wanted.
If I rename or add ports on Subcompositions, it breaks existing connections, which means I need to rewire it up!
Wish I could grab a Comment node by anywhere on, rather than just its mini toolbar. Also—would love support for line breaking (ie, Return, not Enter)
Check the macOS console for crash/error logs. I usually just filter with Vuo to keep it relevant. If you have compiled your own filter/GLSL shader, any errors will also show up there. You can also print to an internal console window in Vuo with the “Display Console Window” node - although it is a bit fumbly with point lists.
Push can be a cumbersome adaptation, but it allows for very fine grain control and optimization of the composition flow. Check out my recent (and perhaps very too long) forum reply here on why I at least think it’s pretty nice!
Q. Aside from the Shift+Command+R to restart a Composition, or right-click on a value, is there any trick to firing off all the Fire on Start nodes? Often I’ve made a change, but find it tedious to reload to see the changes.
Keith, thanks for your feedback. We always appreciate community members’ perspectives. In addition to what has been noted previously:
Often lists/other data is truncated or flows in a way that’s hard for me to see.
We’re going to implement Summarize List Items node in the next release, which should help.
About dragging comments: We decided to make comments only draggable by the titlebar so that you can drag a rubberband within the comment, to easily select multiple nodes that are surrounded by a comment.
And about linebreaks, ⌥↵ (Option-Return) inserts a linebreak in comments and other Vuo text fields. (It’s listed with some other nifty shortcuts in the Keyboard Shortcut section of the manual.)
Again, thanks for your input. Please consider creating feature requests for changes you’d like to see. That way, the rest of the community can add their thoughts (and votes!), allowing us to better understand how a feature would benefit the community as a whole.
