I often option drag say a Process List node and go to rewire it and it wont accept the cables. I am guessing* that this is something to do with the nodes auto-converting to the node variant particular input and output data type.

When nodes are locked to some datatype there could be some visual indication on the node, a symbol or something/anything. When copied nodes should revert to a state as a newly instanced node from the node library. Unless they've been copied with other nodes and still wired to these other nodes.

Please change the FR title to better reflect this request and the underlying issues if this FR is in fact relevant.

Component: 

Comments

Thanks Chris, discovered the

useful design's picture
Submitted by

Thanks Chris, discovered the popups but didn't notice the Revert during the moments when I was pondering this.

I still think it's a barrier to learning that copied nodes don't revert to generic.

It's hard enough with the opacity of some ports refusing to connect to others for no apparent reason for the novice user to have to throw in the wildcard of 'maybe it should connect but you haven't learn about datatype resetting'

We're working on some

jstrecker's picture
Submitted by
Feature status:
Waiting for review by Team Vuo
»
Tabled by Team Vuo

We're working on some usability improvements for generic ports in Vuo 1.3, particularly the process involved in changing from one data type to another. I think they might solve your problem, Alastair (@usefuldesign). I'm tabling this feature request, and we can reevaluate it if needed after the improvements.

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
  • Tabled by Team Vuo