Currently use QC to make custom layers for Bonix TV - a vision mixing kind of application for OS X with a kind of QC stack of layers, each layer being a composition with published ports and some protocols for data types. Also generate sports graphics and twitter feeds and so on for video score boards at large sporting venues.
Spent a few years learning Quartz Composer as my way back into coding from a decade away doing design related work. Film, graphics, studied Architecture for a few years and got involved in publishing then film. Now moving into front side web development. Hope to get into app dev with Vuo and rapid app prototyping.
I used that feature in QC (and the Kineme UI extensions for "split" and "publish" on ports) so much.
I think this has been discussed in the past, and majority opinion seemed to be Vuo has less call for it than QC, but I think it would be a valuable addition. For input ports and output ports, and one to add for all the in or out ports like the Kineme extension offered. Great for when you have to send same data to multiple copies of a node, and as OP says, when refactoring our code.
I'm curious keithlang, what do you use to pan the Editor window with? I would hate to lose spacebar for pan. I'd like to see zoom in and zoom out modifier keys added to it like is standardised in hundreds of graphic design and 3D software.
what about 'control' + 'Spacebar'? or make it user definable in preferences?
If a "Fire all 'Fire at Start nodes'" command was implemented as Vuo menu item then we could assign our own shortcut in the macOS System Preferences > Keyboard Shortcuts> Applications. It should override the panning (or do both) if you set it for spacebar.
regards point 1. I'm open minded on that, haven been using Vuo for ages (will come back) so if that is better in most contexts then sure.
point 3 makes perfect sense. (but point the arrows "forwards" please haha :-) )
Also worth noting that the Node Library pallet window stays on top when one switches to other applications. That’s should not be happening. That should be fixed in my view. In some cases it’s desirable to have one apps floating palettes on top even when in a different application but node palette has no reason to be there in any context that I can think of.