Get it, it's like Code completion. I know, not quite the same thing, but catchy.
From this thread came an idea of warnings if a node would never, could never execute due to lacking input connections.
I think this could be more broadly thought of as 'node completion'
For example, at this very moment I'm using Make Text Field, and it wasn't working. I had forgot to connect the Window.
The Window is all the way at the end of composition. And for almost all Vuo compositions, and certainly for all compositions initially, there is only one window.
In my mind, this seems the kind of thing that's fairly common for people doing interactive design—a bunch of heuristics that produce a single value/event out.
This may not be the right implementation, and perhaps a more constrained version that simply defines cut-off limits per 'bin' is the right approach. But I do think this is the kind of thing that's required a lot when building interactive systems, art, etc. And to implement today in Vuo is quite laborious, or simply too abstract for non-developer-minded people.
That sounds good with one small change: I suggest if you attempt to open a popover that's already open, then it moves the popover/stops the other popover so that the outcome is the same — ie, when the user chooses the menu option, a popover appears in front of the user.
Whilst its not all filters and spinning 3D objects 🙂, there's quite a lot of functionality I had to pack in there to make it usable—for example gesture detection, user preference saving, and a purchase flow (not yet exposed)
