cwilms-loyalist's picture

Yes the "Don't select cables on drag" was what I was think of. Glad to hear it's coming.

jstrecker's picture

Not yet. Node-only selection is on its way: Don't select cables on drag. If you select the nodes and then delete them, the cables attached to them will also be deleted.

jstrecker's picture
@jstrecker commented on @MartinusMagneson's Feature Request, “Don't select cables on drag

We're working on this feature, as sort of a side effect of something else. We'll definitely have key combinations for the first two options: selecting nodes and cables and selecting nodes only. We're planning to make it easier to hide a group of cables by showing a Hide Cables context menu even if the selection also contains nodes.

cremaschi's picture

ArtoolkitX seems an improved and easier library to port.

zimocracy's picture
@zimocracy commented on @zimocracy's Bug Report, “VDMX/VUO

Thank you all for your help! It works perfectly now.

jstrecker's picture

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.

jstrecker's picture
@jstrecker commented on @MartinusMagneson's Discussion, “VuoGenericValue1

No, it won't automatically convert.

If you want the data type's "zero" value, you can do VuoGenericType1_makeFromJson(NULL). This returns 0; (0,0); (0,0,0); or (0,0,0,0) as needed.

For non-zero values, one way to do it is demonstrated in the vuo.math.multiply.list.2 node class's source code. The nodeEvent function calls a (placeholder) function named VuoGenericType1_make1, which is intended to return the "one" value for the appropriate data type. The node class's source code defines a version of the function for each numeric data type — VuoInteger_make1 that returns 1, VuoPoint2d_make1 that returns (1,1), etc. It's long-winded but it works.

MartinusMagneson's picture
@MartinusMagneson commented on @MartinusMagneson's Discussion, “VuoGenericValue1

Thanks! But what I think I mean is, if I scale a VuoGenericInput1 by a real, will the real convert itself to a 2d/3d/4d point as needed? Since the _scale funtion takes scale values in the same format as what they scale that is?

I.e.: Vuo GenericType1 value; VuoReal scale = 0.2; VuoGenericType1_scale(value, (0.2, 0.2)) //for a 2d point?;



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 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.