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.
Comments
Would be good :-)
Would be good :-)
Would developers get to override some input views, say for integers to set upper and lower bounds based on some other inputs on the Node, or a constant in the node code itself?
Alastair (@usefuldesign),
Alastair (@usefuldesign), your comment pertains to to input editors (the interactive thing) rather than input viewers. The ability to customize min/max on a node sounds like a step beyond Turn Share Value into a slider. More advanced cases like setting min/max based on other values might have to be covered by Scriptable Editor.
Jaymie (@jstrecker) I'll move
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:
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
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 Valuenode) 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.