Generic trigger question

Well friends,

I have a definition where iterations (controlled via Anemone) occur (or not) depending upon a variety of conditions (via Gates/Filters/etc). Some iterations feed Kangaroo with data and some not. Most Kangaroo related data are prepared via Anemone Loops.

Anemone is designed to start via trigger events (signaled most commonly by value alterations via sliders or yes/no values via "toggle" components etc etc). When nested, the change of the parent Loop counter triggers the slave Loop sequence etc etc.

The questions is : is there any way for a component (say pull points on curves) to propagate ("emit" some signal) the fact that has finished doing his job? That way one could avoid using delay components and some sort of automation could been achieved.

best, Peter

Replies to This Discussion

Permalink Reply by Mel King on May 29, 2016 at 4:12pm

peter. did you ever figure out a solution to this trigger issue?

Permalink Reply by Andrew Heumann on May 29, 2016 at 8:41pm

I think in the case of the original poster, I believe a simple "list length" component with the input flattened can serve as the trigger - this is a trick I use often to cause one component to execute after another. Does that help?

Permalink Reply by Mohamed Naeim on May 30, 2016 at 5:54am