useful design's picture

Alastair (@usefuldesign)

Groups

  • Vuo Founder

Compositions

1 year ago
useful design's picture

Hi Jaymie when I simply replicate a vuo file the same as yours (Make Color Layer patch only) I don't get the bug.

But when I'm working on sub compositions used in my own Vuo files I consistently have this problem. See screenshot. Attached a sub-composition for you to examine. Try creating an output called acceleration. Not possible for me, Vuo will always append the lowest number not used by another output port already. Even if I delete all the output ports first.

useful design's picture

@adeveloper Can you provide some examples of why that's needed and how that would work using a preference based system please? I'm not sure I understand the need or solution well enough to agree or disagree.

useful design's picture

Without getting into a bike shed type argument about it, having strict datatypes as Vuo does makes it more functional than object oriented I think. I'm not sure if it has lazy evaluational the way QC does for example, another characteristic of a functional language. One of the problems though is the types aren't expansive enough as they stand (no lists of lists for e.g.) and users can only extend types by writing C code.

Any functional language thrives or dies on compositional expressiveness and the ability to create higher level functions from lower level functions. To me sub compositions are not really doing that yet in Vuo, it's too hard to manufacture higher level functions from lower level ones. With QC type Macros as an intermediary step for development I feel like it will engender more of that kind of coding. I agree having too many nodes on the canvas is a deterrent to major work in Vuo.

I'm not smart enough or skilled enough to know if Lambda's in Vuo could be implemented successfully or not. I'm just teaching myself Haskell after a 3 day training course for professional coders run by Lab61 in Australia — I was quickly out of my depth but am totally hooked on the concept of pure functional programming as the coding method of the future.

useful design's picture

Sub-composition published port names get blocked for reuse.

Status: 

Vuo version: 

OS version: 

  • macOS 10.12

How severely does this bug affect you?: 

●●○○ — It's annoying but I can work around it.

Steps causing the bug to occur: 

  1. Create a sub-composition with some published ports
  2. Erase one of the published ports (input or output)
  3. Create a new published port with the same name and place as the erased port (input if erased one was input, output if erased port was output)
  4. Result is the digit "2" appended to the port title.
  5. Rename port to erase the "2" and it becomes a "3"

Have you found a workaround?: 

No.

Other notes: 

It means that when reworking a sub composition you can break wires coming out of it in the parent compositions because it forces a port title change on you which, which obviously breaks the link to other nodes in the parent compositions. Forced to rewire them, and an annoying port name too.

Pages