Status: 

Vuo version: 

OS version: 

  • macOS 10.13

How severely does this bug affect you?: 

●●●○ — It prevents me from completing a specific task with Vuo.

Steps causing the bug to occur: 

  1. Build a subcomposition like on attached image1.
  2. Save in in user library.
  3. Create new composition like on attached image2.
  4. Run and observe events leaving subcomposition (all events should leave it; events from input port outside the subcomposition and also events generated by trigger port inside it – but events triggered inside subcomp. are blocked)

Other notes: 

Also, please, look at the information appearing on problematic trigger port (see image3).

Screenshots: 

Comments

This is intentional behavior.

jstrecker's picture
Submitted by
Status:
Waiting for review by Vuo Support Team
»
Not a bug

This is intentional behavior. See How events travel through a subcomposition, section on "Events out of a subcomposition".

If you used image filter/generator compositions in Vuo 1.x, then you might recall that you had to be really careful about using triggers, because there had to be a one-to-one correspondence between events entering and events exiting the composition. We changed that in Vuo 2.0 so that the burden is no longer on you to be cautious. The behavior you're seeing is related to that. It also prevents certain kinds of infinite feedback loops.