jstrecker's picture

@timwessman, great to hear that you're coding with the Vuo framework. Try this:

void nodeEvent(VuoOutputData(VuoOscMessage) message)
{
    struct json_object *data[1] = { json_object_new_double(1.23) };
    VuoOscType     dataTypes[1] = { VuoOscType_Auto };
    *message = VuoOscMessage_make(VuoText_make("/foo"), 1, data, dataTypes);
}
timwessman's picture
useful design's picture

Reversible node orientation (flipped) on canvas to untangle wires of feedback type nodes

This concept came to me from an dynamic system modelling tool called Minsky which uses a visual programming type canvas, node and wires interface. Example

Quite often we'll have one or more nodes in any functional group of nodes where the inputs are being fed from nodes to the right and the output is going to nodes on the left. No amount of rearranging the nodes will avoid wires running right to left. Flipping the node about a vertical axis would put the input(s) on the right and output port(s) on the left.

If the redesign of Vuo results in nodes being asymmetric in the horizontal plane then flipped nodes would be more readily apparent than otherwise, and no additional visual cue would be required. If nodes frames are symmetrical, then a right to left arrow at top or bottom of node could be useful.

Here's an example of asymmetric node design, design appropriated from an old nord synth app.

useful design's picture

Jaymie (@jstrecker) It's not clear to me what port design has been adopted for the redesign (inside like QC/Origami, half-inside-half-outside like current or completely detached like [insert vis. prog. tool here]). Either way I think when you have enough wires, especially when they come in at angles closer to the vertical than horizontal and the are wires are all straight there's going to be trouble tracing them. That's what the colour coding thing would solve. Maybe people consider it more trouble than it's worth. (Caps-lock or a shortcut could turn the feature on and off).

In terms of current Vuo vs QC/Origami I find it just as easy to get a bit confused about wire origins/destinations at times and having the ports half slung off the edge of the node is never something I particular took to in an aesthetic (see video link) and did sense any improved functional capability over QC/Origami port design. If a more functionally discriminating GUI can be worked out my solution of colour coding selected node wires would be less relevant.

Another feature request I've been sitting on, reversible patch orientation (horizontal flip for nodes) would also help de-clutter the canvas. Will add that FR now.

Admiral Ackbar - "It's A Trap!"

jstrecker's picture
@jstrecker commented on @Bodysoulspirit's Feature Request, “Get File Drags On App Icon

Thanks for the suggestion, @Bodysoulspirit. Opened for voting.

jstrecker's picture

Alastair (@usefuldesign), since there are significant design changes coming in the next major release (thanks to suggestions from you and others in the community), let's reassess after that: is wire tracing still a problem, and if so, how would rainbow cables or other solutions work out with the new design?

Pages

Welcome!

Vuo is more than nodes and cables, it's a community! Feel free to browse or add your voice.

Browse Discussions

Start a Discussion


Browse Questions and Answers

Ask a Question


Browse Feature Requests

Suggest a Feature


Browse the Composition Gallery

Share a Composition


How can I get notifications?

Learn more about the community

Learn more about Vuo

Vuo Announcements

Sign up for the Vuo announcements mailing list to get news and join the community. We post about once per month.