marcorexo1's picture



marcorexo1's picture
marcorexo1 posted a new Feature Request, “Keeping event port visible

Keeping event port visible


I'm learning Vuo and am no expert yet. So this suggestion is based on my current understanding.

I have noticed that the refresh ports are not visible as they are in Vuo Editor 1.2.8. I'm thinking that simplifying nodes in this way could make it more difficult for learners to understand how Vuo works.

Do you think that keeping the refresh ports visible for each node, such as in Vuo Editor 1.2.8, is a good idea for students who also learn textual programming tools? My reasons:

  1. A visible refresh port makes the difference between refresh signals and method arguments more clear.
  2. Some nodes refresh port signal could be compared to a call to instantiation? Some nodes require a signal from 'Fire on Start' to be rendered. So if a direct comparison is made with a textual programming language this comparison will be more easily made.
  3. I think it's easier to understand how Vuo works by revealing the port.


marcorexo1's picture
marcorexo1 posted a new Composition, “Bacteria vs penicillin

Bacteria vs penicillin

A simulation showing that bacteria which randomly land within the Petri dish are selected to die whereas those outside are selected to live on (green).

Future improvement 1) A method to reduce the bacteria population inside the Petri dish as they begin to die. 2) Better implementation so that the first green oval in the centre of the dish is removed. 3) Add user GUI to reset composition or change simulation conditions.

Composition and supporting files: 

Exported App: 

marcorexo1's picture

Bodysoulspirit your composition is what I was attempting to make. Thank you both.

marcorexo1's picture
marcorexo1 posted a new Discussion, “Append layers to a list during runtime
marcorexo1's picture
marcorexo1 commented on marcorexo1's Discussion, “Refactor this composition

Thank you for your time - wow I was making some spaghetti code.