Bonsai
Replies: 2 comments 4 replies
-
|
Please attach the workflow. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Sure here's a little example workflow (added .txt extension to upload): there an accumulator with +1/-1 on up/down keypress, the ending SkipWhile node should filter out elements whenever they're >5, but instead it passes all elements through (I did end up solving my original issue with a Scan, but good to know about this for future reference) |
Beta Was this translation helpful? Give feedback.
-
|
Not sure I see the problem. The operator states: "... bypasses elements in an observable sequence as long as the condition specified by the encapsulated workflow is true.". Is it the case you thought the boolean logic was reversed? |
Beta Was this translation helpful? Give feedback.
-
|
Ah I see, I misinterpreted "SkipWhile will start emitting all elements from the source sequence" - I thought this was dynamic (would turn on and off depending on condition) rather than on a switch (off at start, then on permanently once the condition is true), thanks. |
Beta Was this translation helpful? Give feedback.
-
|
That behavior you describing is implemented using the Condition operator. |
Beta Was this translation helpful? Give feedback.
-
|
Oh perfect, thanks! I didn't realize condition worked like that. |
Beta Was this translation helpful? Give feedback.
-
Hi - I have a question about the SkipWhile: the documentation seems very clear, but this node doesn't seem to perform as expected. Here's an example below, where the conditions in SkipWhile are fullfilled (workflowoutput is true), but the SkipWhile node continues to pass elements. Am I using this incorrectly?
Beta Was this translation helpful? Give feedback.
All reactions