On 3/17/21 6:29 PM, adam johnson wrote:
and i was only saying that just because something is implemented in
such-and-such way should be of no concern.
A feature not existing because of the difficulty of adding it would be one
possible answer to my question, so I checked the code before coming
hello,
[trigger b b b b]
||||
DCBA
will do to A, B, C and D.
if you want to do C and D only depending of the result of B, the best "pd"
solution is not to stop the trigger. You should use 2 trigger :
[trigger b b]
||
BA
|
[test result]
|
[select 1]
|
[trigger b
>and i was only saying that just because something is implemented in
>such-and-such way should be of no concern.
A feature not existing because of the difficulty of adding it would be one
possible answer to my question, so I checked the code before coming here
and it turned out to be the expected
On 3/17/21 9:20 AM, adam johnson wrote:
I guess I was not clear, I am not using it as a loop, I was just saying
that at the code level [trigger] is a for loop, so having it break would be
simple to add.
and i was only saying that just because something is implemented in
such-and-such way
I guess I was not clear, I am not using it as a loop, I was just saying
that at the code level [trigger] is a for loop, so having it break would be
simple to add. I am using it more as a conditional, if certain conditions
are met on this output, it bangs the right inlet and stops the rest. This
is
On 3/17/21 9:39 AM, adam johnson wrote:
Sometimes when using trigger I find myself needing to break out of it
before it completes, simple to work up an abstraction to handle this,
but it got me to wondering why trigger does not have a right inlet to
stop the sequence. Looking at the code,
Sorry, I forgot to reply to the list.
Hello Adam,
I am not sure how you are using trigger like a for loop Can you send an
example?
The way I use trigger is to make sure the incoming message is output in the
order I want them to (from right to left).
Maybe you can use a spigot after each output.