There's currently an API for input editors — to customize the widget that pops up when you double-click on an input port to edit the port's constant value.

This feature request is to add an API for input viewers — to customize how input port data is displayed in a constant flag and how input/output port data is displayed in a port popover. This API would be available to any node developers, but just to give a sense of it, here are a couple of examples of how I envision it being used by Team Vuo:

  • For Image ports, display a preview of the image in port popovers.
  • For Font ports, make the text font and color in the constant flag match the chosen font.

Component: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo and Vuo Pro licenses

Complexity: 

●●○○ — A few weeks of work

Potential: 

●○○ — Appeals to current community

Comments

Jaymie (@jstrecker) I'll move

useful design's picture
Submitted by

Jaymie (@jstrecker) I'll move this to another FR, please let me know which one, but one thing that I've constantly asked for in Vuo since pre-Alpha days even because it was such a frustrating limitation for me in QC when building applications with QCBuilder or layers for other Apps. Layers for Vision mixing/presentation software mostly in my case but also stand alone apps, In the editor obviously you can alter the published input datatypes with the Setttings Panel (⌘2 shortcut). But not depending on state of a running composition programatically which is my desired function here. Starting with Min/Max vapes on sliders but ideally all input type and value definitions for published inputs.

Scriptable Editor wouldn't do it because it needs to operate in the compiled application even running in VDMX or stand alone application.

Examples:

  • change the range a numeric slider can operate in and the step value
  • change from integer number input to real number input
  • change the options on a enumerated list (known as a labelled index input in QC) to be context appropriate (i.e. change the list items on the fly) or grey menu item options out; or for that matter hide and show inputs according to other inputs or program state.
  • programatically change the input the user sees to reflect a change of state generated within the composition. e.g. sides on a shape, left and right arrow keys increase and decrease the number of sides. Sometimes you want to enter a number or see the number of sides, be nice if the input kept up with the state change within the composition to reflect current number of sides to the shape.

It's something that turns out would be incredibly useful in making QC/Vuo layers more functional and UI powerful if we could perform these more Cocca like nice tricks.

depending on state of a

jstrecker's picture
Submitted by

depending on state of a running composition programatically

Alastair (@usefuldesign), since that's not covered by an existing feature request, you should create a new one. On that FR, it would be helpful if you could give specific examples of situations where the Edit Details context menu (exists for published input ports, proposed for the Share Value node) would not suffice. I understand that you're requesting something more dynamic than Edit Details, but I'm not yet understanding what you want to use it for.

Feature status

When we (Team Vuo) plan each release, we try to implement as many of the community's top-voted feature requests as we have time for. Vote your favorite features to the top! (How do Vuo feature requests work?)

  • Submitted to vuo.org
  • Reviewed by Team Vuo
  • Open for community voting
  • Chosen to be implemented
  • Released